-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Ingest Manager] Log level reloadable from fleet #22690
[Ingest Manager] Log level reloadable from fleet #22690
Conversation
Pinging @elastic/ingest-management (Team:Ingest Management) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great. Just 2 comments.
@@ -26,8 +26,11 @@ const agentInfoKey = "agent" | |||
// defaultAgentActionStoreFile is the file that will contains the action that can be replayed after restart. | |||
const defaultAgentActionStoreFile = "action_store.yml" | |||
|
|||
const defaultLogLevel = "debug" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this change can we move the default up to info?
Debug level is still causing duplicate events, which still needs to be solved even in debug.
zapLevel = zapcore.ErrorLevel | ||
} | ||
|
||
return zapLevel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't there something that already does this in libbeat? Couldn't we change that to expose it, instead of implementing it here.
[Ingest Manager] Log level reloadable from fleet (elastic#22690)
[Ingest Manager] Log level reloadable from fleet (elastic#22690)
* [Ingest Manager] Log level reloadable from fleet (#22690) [Ingest Manager] Log level reloadable from fleet (#22690) * aa * create drop * updated drop * process contains everything * drop start time * undo exposed endpoint * sanitize dataset name * ups * agent expose http * collect all metrics from beats * colelct all from beats * golint * cleaner docs * updated structure * cgroup * long live file saving issues
* [Ingest Manager] Log level reloadable from fleet (elastic#22690) [Ingest Manager] Log level reloadable from fleet (elastic#22690) * aa * create drop * updated drop * process contains everything * drop start time * undo exposed endpoint * sanitize dataset name * ups * agent expose http * collect all metrics from beats * colelct all from beats * golint * cleaner docs * updated structure * cgroup * long live file saving issues (cherry picked from commit 49c8d87)
…23105) * [Ingest Management] Agent expose metrics (#22793) * [Ingest Manager] Log level reloadable from fleet (#22690) [Ingest Manager] Log level reloadable from fleet (#22690) * aa * create drop * updated drop * process contains everything * drop start time * undo exposed endpoint * sanitize dataset name * ups * agent expose http * collect all metrics from beats * colelct all from beats * golint * cleaner docs * updated structure * cgroup * long live file saving issues (cherry picked from commit 49c8d87) * Add changelog. Co-authored-by: Michal Pristas <[email protected]>
What does this PR do?
This PR introduces log level reloading initiated by SETTINGS action coming from fleet introduced in this PR: elastic/kibana#83707
This strategy reexecs agent on log level change.
Why is it important?
#20756
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.