-
Notifications
You must be signed in to change notification settings - Fork 523
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
Translate OpenTelemetry system metrics #5796
Comments
@axw I love your initiative. Did you evaluate how we should prioritize the "official" system metrics versus the metrics captured by the OpenTelemetry Collector receiver for Host Metrics? I did some research when filling Map the metrics of the OpenTelemetry Collector Host Metrics Receiver to ECS and store them in the metrics- indices #5310 and it seemed that few of them were slightly different. Maybe you have a different perspective . |
Related: elastic/kibana#105923. We're not collecting the CPU and thread count metrics for JVM OpenTelemetry. |
@cyrille-leclerc no, I did not do any kind of evaluation - I just opened this for tracking. |
add comments for Tracking |
Is there any development regarding this issue? |
Hi, Is there any update on this for dotnet? |
Still nothing with 8.11.3 version. Only traces and logs show up. |
Similar to what we did for JVM metrics (#4919), we should translate OpenTelemetry system metrics to the equivalent metrics produced by Elastic APM agents, if possible, so they appear under the service overview metrics in Kibana.
The text was updated successfully, but these errors were encountered: