-
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] Fix refresh of monitoring configuration #23619
[Ingest Manager] Fix refresh of monitoring configuration #23619
Conversation
Pinging @elastic/ingest-management (Team:Ingest Management) |
Pinging @elastic/agent (Team:Agent) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
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.
Looks good to me.
Looks like the unit test does good coverage of if this is actually working now. Lets land it and get some real world testing on it.
/package |
I pulled the branch gcp agent artifact for linux .tar.gz and tested it out and the logging seems to be turned off or on exactly as policy states without problem now. this is great, nice work Michal |
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.
tests like it works to me.
* fix refresh of monitoring beats * more descriptive comment * changelog * newline
* fix refresh of monitoring beats * more descriptive comment * changelog * newline
What does this PR do?
This PR fixes few things
tests for decorator were out of date
More sensitive monitoring change detection.
We were only regenerating on program list change now we regenerate even on internal config change
Generate monitoring steps for operator not only when switch is changed but also when config is changed for agent and monitoring is running. New config will be generated and picked up by monitoring beats.
Why is it important?
Fixes: #23599
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.