-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Elastic Agent] Allow Metricbeat metricsets to report their status to the Elastic Agent #39736
Labels
Team:Elastic-Agent-Data-Plane
Label for the Agent Data Plane team
Comments
cmacknz
added
the
Team:Elastic-Agent-Data-Plane
Label for the Agent Data Plane team
label
May 24, 2024
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
#39737 is an obvious candidate to do alongside this one, but we could also pick a metricset that requires a username/password combination as it will have a much clearer criteria for when to report the failed state. |
This was referenced Jun 21, 2024
@jlind23 @pierrehilbert attaching the screenshot of Kibana with a custom build. |
6 tasks
6 tasks
Waiting on #40298 |
6 tasks
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #39735 a status reporter was passed into the Beats object reloader and propagated through to Filebeat inputs via the input V2 interface.
Identify how to propagate the status reporter into Metricbeat metricsets to allow them to report their status to the Elastic Agent when they encounter errors.
Choose a metricset to use as a reference implementation and have it report errors using the control protocol.
The text was updated successfully, but these errors were encountered: