You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 21, 2023. It is now read-only.
Fleet exposes a metric dashboard for each enrolled agent, with output metric broken down by each process making a connection to Elasticsearch. A screenshot of this dashboard is below:
How should we update this dashboard when the agent is using the shipper? The output statistics are currently grouped by beat.type by default. Should we continue doing this? Will aggregating by beat type continue to work with the shipper implementation where the output is no longer per beat?
Should we group by data stream or input source instead and obsolete the beat.type parameter?
Fleet exposes a metric dashboard for each enrolled agent, with output metric broken down by each process making a connection to Elasticsearch. A screenshot of this dashboard is below:
How should we update this dashboard when the agent is using the shipper? The output statistics are currently grouped by
beat.typeby default. Should we continue doing this? Will aggregating by beat type continue to work with the shipper implementation where the output is no longer per beat?Should we group by data stream or input source instead and obsolete the
beat.typeparameter?Design document: https://docs.google.com/document/d/18bYC5IshBhVoIRXmbDCA8Ga8UD1mrrgtUlmhPeoWqoU/edit