-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Fleet] Pass policy namespace to agent monitoring settings #100500
Conversation
Pinging @elastic/fleet (Team:Fleet) |
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.
Seems small enough to approve 👍
💚 Build SucceededMetrics [docs]Async chunks
Unknown metric groupsReferences to deprecated APIs
To update your PR or re-run it, just comment with: cc @jen-huang |
…00500) * Pass agent policy namespace to agent monitoring settings * Adjust copy
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
…100511) * Pass agent policy namespace to agent monitoring settings * Adjust copy Co-authored-by: Jen Huang <[email protected]>
We have validated this PR #100500 on 7.14 snapshot cloud-qa build and found that working fine.
Build Details:
Please let us know if we are missing anything. Thanks |
Summary
Resolves #98542. This PR passes the agent policy namespace to the
agent.monitoring
settings in generated agent YAML. Note that this needs corresponding changes on agent side before it actually affects where the monitoring data goes (elastic/beats#25350) but this PR can go in first.