-
Notifications
You must be signed in to change notification settings - Fork 204
Description
The Elasticsearch exporter introduced connection health reporting, which will make it's way into Elastic Agent as Beats begin running as receivers starting with the monitoring Beats.
This is the initial introduction of output health and we may find that it has bugs or is too sensitive, so add the ability to mute the problems it detects in cases where a bug fix is needed. It is also the case that the Fleet UI does not visualize output health as well as input health (yet) so this also gives us the option to hide the feature until we are ready to have it work properly end to end.
Ideally, this would be configured per output and can be a toggle in the advanced YAML settings box. This avoids the need to build any additional UI around this toggle. This would have Elastic Agent receiver configuration like below but introduce the requirement to track the state of the toggle per input.
outputs:
default:
type: elasticearch:
status_reporting:
enabled: falseWe could also potentially add this at the agent policy level, perhaps grouping it with the collector settings. This would likely be simpler to implement but require a new setting in the agent policy settings UI or a call to the policy override API to set until a toggle can be added directly in the UI.
agent:
collector:
status_reporting:
enabled: false