Skip to content

[9.3] [Fleet] Fix selected log level when there is a policy override (#259425)#259779

Merged
kibanamachine merged 1 commit intoelastic:9.3from
kibanamachine:backport/9.3/pr-259425
Mar 26, 2026
Merged

[9.3] [Fleet] Fix selected log level when there is a policy override (#259425)#259779
kibanamachine merged 1 commit intoelastic:9.3from
kibanamachine:backport/9.3/pr-259425

Conversation

@kibanamachine
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 9.3:

Questions ?

Please refer to the Backport tool documentation

…ic#259425)

If agent configuration contains no log level, the one in the assigned
policy should be used, instead of the default one (`info`).

Aims to help on some issues we are investigating related to agents going
back to the `info` logging level when they have a different one
configured per-policy or per-agent.

In real cases the log level should never be undefined at this point, but
just in case, ensure that the expected one is used instead of `info`.

(cherry picked from commit 2be40e3)
@kibanamachine kibanamachine added the backport This PR is a backport of another PR label Mar 26, 2026
@kibanamachine kibanamachine enabled auto-merge (squash) March 26, 2026 13:34
@botelastic botelastic bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Mar 26, 2026
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/fleet (Team:Fleet)

@elasticmachine
Copy link
Copy Markdown
Contributor

@kibanamachine kibanamachine merged commit d91ff62 into elastic:9.3 Mar 26, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR Team:Fleet Team label for Observability Data Collection Fleet team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants