[Fleet] Fix selected log level when there is a policy override#259425
Merged
jsoriano merged 2 commits intoelastic:mainfrom Mar 26, 2026
Merged
[Fleet] Fix selected log level when there is a policy override#259425jsoriano merged 2 commits intoelastic:mainfrom
jsoriano merged 2 commits intoelastic:mainfrom
Conversation
jsoriano
added
release_note:fix
Team:Fleet
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
juliaElastic
approved these changes
Mar 25, 2026
Contributor
|
Starting backport for target branches: 8.19, 9.2, 9.3 https://github.com/elastic/kibana/actions/runs/23596656664 |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
cc @jsoriano |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Mar 26, 2026
…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
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Mar 26, 2026
…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)
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
shahargl
pushed a commit
to shahargl/kibana
that referenced
this pull request
Mar 26, 2026
…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`.
kibanamachine
added a commit
that referenced
this pull request
Mar 26, 2026
…259425) (#259779) # Backport This will backport the following commits from `main` to `9.3`: - [[Fleet] Fix selected log level when there is a policy override (#259425)](#259425) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jaime Soriano Pastor","email":"jaime.soriano@elastic.co"},"sourceCommit":{"committedDate":"2026-03-26T13:23:59Z","message":"[Fleet] Fix selected log level when there is a policy override (#259425)\n\nIf agent configuration contains no log level, the one in the assigned\npolicy should be used, instead of the default one (`info`).\n\nAims to help on some issues we are investigating related to agents going\nback to the `info` logging level when they have a different one\nconfigured per-policy or per-agent.\n\nIn real cases the log level should never be undefined at this point, but\njust in case, ensure that the expected one is used instead of `info`.","sha":"2be40e3fb7782e93e058ba417eeeeba8aba1ed08","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","sdh-linked","backport:all-open","v9.4.0"],"title":"[Fleet] Fix selected log level when there is a policy override","number":259425,"url":"https://github.com/elastic/kibana/pull/259425","mergeCommit":{"message":"[Fleet] Fix selected log level when there is a policy override (#259425)\n\nIf agent configuration contains no log level, the one in the assigned\npolicy should be used, instead of the default one (`info`).\n\nAims to help on some issues we are investigating related to agents going\nback to the `info` logging level when they have a different one\nconfigured per-policy or per-agent.\n\nIn real cases the log level should never be undefined at this point, but\njust in case, ensure that the expected one is used instead of `info`.","sha":"2be40e3fb7782e93e058ba417eeeeba8aba1ed08"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/259425","number":259425,"mergeCommit":{"message":"[Fleet] Fix selected log level when there is a policy override (#259425)\n\nIf agent configuration contains no log level, the one in the assigned\npolicy should be used, instead of the default one (`info`).\n\nAims to help on some issues we are investigating related to agents going\nback to the `info` logging level when they have a different one\nconfigured per-policy or per-agent.\n\nIn real cases the log level should never be undefined at this point, but\njust in case, ensure that the expected one is used instead of `info`.","sha":"2be40e3fb7782e93e058ba417eeeeba8aba1ed08"}}]}] BACKPORT--> Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
Mar 27, 2026
…259425) (#259778) # Backport This will backport the following commits from `main` to `9.2`: - [[Fleet] Fix selected log level when there is a policy override (#259425)](#259425) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jaime Soriano Pastor","email":"jaime.soriano@elastic.co"},"sourceCommit":{"committedDate":"2026-03-26T13:23:59Z","message":"[Fleet] Fix selected log level when there is a policy override (#259425)\n\nIf agent configuration contains no log level, the one in the assigned\npolicy should be used, instead of the default one (`info`).\n\nAims to help on some issues we are investigating related to agents going\nback to the `info` logging level when they have a different one\nconfigured per-policy or per-agent.\n\nIn real cases the log level should never be undefined at this point, but\njust in case, ensure that the expected one is used instead of `info`.","sha":"2be40e3fb7782e93e058ba417eeeeba8aba1ed08","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","sdh-linked","backport:all-open","v9.4.0"],"title":"[Fleet] Fix selected log level when there is a policy override","number":259425,"url":"https://github.com/elastic/kibana/pull/259425","mergeCommit":{"message":"[Fleet] Fix selected log level when there is a policy override (#259425)\n\nIf agent configuration contains no log level, the one in the assigned\npolicy should be used, instead of the default one (`info`).\n\nAims to help on some issues we are investigating related to agents going\nback to the `info` logging level when they have a different one\nconfigured per-policy or per-agent.\n\nIn real cases the log level should never be undefined at this point, but\njust in case, ensure that the expected one is used instead of `info`.","sha":"2be40e3fb7782e93e058ba417eeeeba8aba1ed08"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/259425","number":259425,"mergeCommit":{"message":"[Fleet] Fix selected log level when there is a policy override (#259425)\n\nIf agent configuration contains no log level, the one in the assigned\npolicy should be used, instead of the default one (`info`).\n\nAims to help on some issues we are investigating related to agents going\nback to the `info` logging level when they have a different one\nconfigured per-policy or per-agent.\n\nIn real cases the log level should never be undefined at this point, but\njust in case, ensure that the expected one is used instead of `info`.","sha":"2be40e3fb7782e93e058ba417eeeeba8aba1ed08"}}]}] BACKPORT--> Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
jsoriano
added a commit
that referenced
this pull request
Mar 27, 2026
jeramysoucy
pushed a commit
to jeramysoucy/kibana
that referenced
this pull request
Apr 1, 2026
…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`.
paulinashakirova
pushed a commit
to paulinashakirova/kibana
that referenced
this pull request
Apr 2, 2026
…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`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
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
infologging 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.Issue found while investigating with AI assistant
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.