-
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
Cherry-pick #18091 to 7.x: Use default output by default #18119
Conversation
[Elastic-Agent] Use default output by default (elastic#18091)
Pinging @elastic/ingest-management (Project:fleet) |
💚 Build SucceededExpand to view the summary
Build stats
|
@@ -25,6 +25,8 @@ | |||
- Fixed injected log path to monitoring beat {pull}17833[17833] | |||
- Make sure that the Elastic Agent connect over TLS in cloud. {pull}17843[17843] | |||
- Moved stream.* fields to top of event {pull}17858[17858] | |||
- Fix an issue where the checkin_frequency, jitter, and backoff options where not configurable. {pull}17843[17843] |
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.
backport issues?
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.
Just update the changelog
Cherry-pick of PR #18091 to 7.x branch. Original message:
What does this PR do?
Releases neccesity of having
use_output
specified with monitoring settings.if not output is specified the one called
default
is usedWhy is it important?
Default configurations does not state use output settings so this might be confusing
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.