Cherry-pick #19114 to 7.x: Rename to management.Manager, add UpdateStatus to Manager interface. #19172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #19114 to 7.x branch. Original message:
What does this PR do?
Renames
management.ConfigManager
tomanagement.Manager
being that it now does more than just manage configurations. AddsUpdateStatus
tomanagement.Manager
to allow a beat to update the status.Using
FleetManager
the status will be propagated over theelastic-agent-client
to the controlling agent.Why is it important?
So status can be reported both to the controlling Agent and up to Fleet for observability of the beats that Agent is running.
Reporting a
Failed
status to Agent will result in the Agent stopping and restarting the beat.Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
HealthCheck
function in every beats. #17737Use cases
Screenshots
Logs