Cherry-pick #19114 to 7.x: Rename to management.Manager, add UpdateStatus to Manager interface.#19172
Conversation
…lastic#19114) * Rename management.ConfigManager to management.Manager, add UpdateStatus to Manager interface. * Update docstring for Failed status. * Add to developer changelog. * Add StatusReporter interface, wrap client.Status in lock. Add tests for statusToProtoStatus. (cherry picked from commit 05c9065)
|
Pinging @elastic/integrations-services (Team:Services) |
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
Cherry-pick of PR #19114 to 7.x branch. Original message:
What does this PR do?
Renames
management.ConfigManagertomanagement.Managerbeing that it now does more than just manage configurations. AddsUpdateStatustomanagement.Managerto allow a beat to update the status.Using
FleetManagerthe status will be propagated over theelastic-agent-clientto 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
Failedstatus 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.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues
HealthCheckfunction in every beats. #17737Use cases
Screenshots
Logs