-
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] Sending monitoring metrics to logs datastream #26758
Comments
Pinging @elastic/agent (Team:Agent) |
Beats logs its metrics every 30s. This was built before there was even a metrics endpoint in Beats. Elastic Agent behaves as expected here as it just "tails" the log file. Instead we should likely disable the logging of these metrics which I think can be done through a config option. I remove the |
We'll add a config option to disable logging metrics. However the default behaviour will not change as we may need access to these metrics (through the log files) to help us debug issues. |
@ruflin, my PR adds a setting that can be used in stand-alone mode to stop the beats from emitting metrics. If we want this to be enabled in fleet mode, the setting should be passed as part of the policy, and set through Kibana. I'm not sure what project (fleet/kibana) is responsible for doing that/where to make the issue. |
I don't think we should build any short term hacks around this and I'm also not sure on the urgency. @jen-huang As soon as there is a config option, we could like use this as the default in the policy? |
Each agent policy needs to explicitly declare what agent monitoring options should be enabled, by default it is stored as We could add a migration for 7.15 to add it to existing policies though. But I think we will want some conditional logic there, I suppose |
They are decoupled it's possible to enable The default settings will not change from the current behaviour (metrics appear in logs). |
We are reusing |
It looks like Elastic Agent is sending it's own monitoring metrics to the logs datastream. This is not useful as a log message. It should be sending this information to the metrics datastream instead.
Example event:
For confirmed bugs, please report:
The text was updated successfully, but these errors were encountered: