Stop self monitor output health reporting if output config is not ack…

[juliaElastic]

…ed by agents

What is the problem this PR solves?

Output health kept reporting incorrect state after output config was updated, but the new config was not yet acked by any agents.

How does this PR solve the problem?

Self monitor compares the current bulker output config with the latest output config from .fleet-policies. If the bulker doesn't use the latest config, the self monitor will stop reporting output health until an agent acks it.

How to test this PR locally

• Create a remote es output that points to a second ES
• Enroll an agent that uses the remote es
• Update the remote es config to point to an invalid host
• The output health UI should show the connection error
• Stop the agent
• Update the remote es config to point to a valid host again
• The output health UI should clear
• Re-start the agent
• The output health UI should show healthy status

output_health.mov

Design Checklist

• I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.
• I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.
• I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool

Related issues

Closes #3334

[elastic-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[nchaulet]

code LGTM 🚀