-
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] Change monitoring defaults for agent #18927
[Ingest Manager] Change monitoring defaults for agent #18927
Conversation
Pinging @elastic/ingest-management (Team:Ingest Management) |
…as/beats into agent-default-monitoring-cfg
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.
LGTM
logs: true | ||
# enables metrics monitoring | ||
metrics: true | ||
# settings.monitoring: |
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.
In Beats we tried not to have a space after #
for the things that are actual settings. Like this commenting out is easier and it is more obvious what is a setting and what a description.
Also below we have for the comments two #
which I think makes it less readable.
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.
will handle in separate PR
[Ingest Manager] Change monitoring defaults for agent (elastic#18927)
[Ingest Manager] Change monitoring defaults for agent (elastic#18927)
What does this PR do?
At this point monitoring is disabled by default, this PR makes it enabled and removes the necessity to have monitoring configuration in a configuration file
Why is it important?
Less things user needs to worry about
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Continuation of #18226