# Miss metrics in APM service when using opentelemetry agent for Java/Node.js

**URL:** https://discuss.elastic.co/t/miss-metrics-in-apm-service-when-using-opentelemetry-agent-for-java-node-js/365009
**Category:** Elastic Observability
**Created:** [August 16, 2024, 8:57am UTC](https://discuss.elastic.co/t/miss-metrics-in-apm-service-when-using-opentelemetry-agent-for-java-node-js/365009 "2024-08-16T08:57:15Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Gary\_Liu1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gary_liu1/32/122430_2.png) [@Gary\_Liu1](https://discuss.elastic.co/u/Gary_Liu1)
#### Post date: [August 16, 2024, 8:57am UTC](https://discuss.elastic.co/t/miss-metrics-in-apm-service-when-using-opentelemetry-agent-for-java-node-js/365009/1 "2024-08-16T08:57:15Z")

</div>

I'm using OpenTelemetry auto-instrumentation in OpenShift to collect java & node.js application data to Elastic APM, can find new services of the Pod but missing some expected metrics compare to APM agent:  
Java: no 'system memory usage', says 'no data to display'  
Node.js: worse and only display 2 panels 'system memory usage' and 'system memory utilization' with error message ' \* Field **system.memory.usage** was not found.‘, and no other panel like CPU etc.  
Any one can guide me how to troubleshot this issue?