-
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
Give precedence to monitoring reporter hosts over output hosts #17991
Conversation
Pinging @elastic/stack-monitoring (Stack monitoring) |
Pinging @elastic/integrations-services (Team:Services) |
Change looks ok. But pleaes check changelog and the intake job failing. |
979bed4
to
9ecfdf9
Compare
💔 Build FailedExpand to view the summary
Build stats
Test stats 🧪
Log outputExpand to view the last 100 lines of log output
|
1dee5f8
to
8c0ddb0
Compare
CI failures are unrelated. Merging. |
… (#18301) * Give precedence to monitoring reporter hosts over output hosts * Add CHANGELOG entry * Removing debugging statements * No delete * Helper function * Make new config if nil * Formatting code
… (#18215) * Give precedence to monitoring reporter hosts over output hosts * Add CHANGELOG entry * Removing debugging statements * No delete * Helper function * Make new config if nil * Formatting code
…17991) (#18216) * Give precedence to monitoring reporter hosts over output hosts (#17991) * Give precedence to monitoring reporter hosts over output hosts * Add CHANGELOG entry * Removing debugging statements * No delete * Helper function * Make new config if nil * Formatting code * Clean up CHANGELOG
…lastic#17991) (elastic#18216) * Give precedence to monitoring reporter hosts over output hosts (elastic#17991) * Give precedence to monitoring reporter hosts over output hosts * Add CHANGELOG entry * Removing debugging statements * No delete * Helper function * Make new config if nil * Formatting code * Clean up CHANGELOG
What does this PR do?
Ensures that monitoring reporter hosts, if set, get total precedence over their corresponding output reporter hosts.
Why is it important?
When monitoring reporter hosts are configured, they should get precedence over their corresponding output hosts. The two lists of hosts should not be merged.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues