Skip to content

logging: level being passed as log-options is not interpreted #16002

@mvisonneau

Description

@mvisonneau

Bug report

I spotted that we do not properly interpret the level of the --log-options, therefore we cannot really update the logging level. At first sight, I believe the culprit resides in here:

setLogLevelFromOptions(logOptions)

This variable does not seem to be updated at any point.

I will work on a PR to sort this issue out and make the logging level interface easier to use.

General Information

  • Cilium version: v1.9.4 - though it probably impacts much lower versions too

How to reproduce the issue

  • Attempt to start the agent with --log-options='{"level":"error"}'

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/agentCilium agent related.kind/bugThis is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.pinnedThese issues are not marked stale by our issue bot.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions