# "No JVMs were found" in JVM tab after APM upgrade from 1.38 to 1.43

**URL:** <https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537>\
**Category:** APM\
**Tags:** java, agent-explorer\
**Created:** [November 6, 2023, 3:17pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537 "2023-11-06T15:17:03Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jandry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jandry/32/126754_2.png) [@jandry](https://discuss.elastic.co/u/jandry)\
**Post date:** [November 6, 2023, 3:17pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/1 "2023-11-06T15:17:03Z")

</div>

**Kibana version** :  
7.16.3

**APM Jva agent version** :  
1.43

Hi,  
For my previous ticket we did an upgrade of our apm agent from 1.38 to 1.43 and only that

> [@Spring controller hiden behind DispatcherServlet#do\*](https://discuss.elastic.co/t/spring-controller-hiden-behind-dispatcherservlet-do/345548):
>
> Kibana version: 7.16.3 I got exctly the same issue as [Remove spring DispatcherServlet from transactions - #18 by ethranes](https://discuss.elastic.co/t/remove-spring-dispatcherservlet-from-transactions/187147/18) See screenshot [image] I'm using Spring Boot 3.0.x with agent elastic-apm-agent-1.36.0.jar I tried given solution that seems to be adding following parameter to my agent ELASTIC\_APM\_DISABLE\_INSTRUMENTATIONS=servlet-api but I still have same behaviour. Any additional recommandation on this ?

We now have the transaction correctly but we lost the JVM tab

But we lost the JVM metrics

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/a/6a6d8f260ec82f6f49522848c2ba579b9572d6a8.png)

Any known issue about that ?  
I found old tickets about that asking to upgrade to older version than mine

Regards

---

<div class="post-metadata">

**Author:** ![jandry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jandry/32/126754_2.png) [@jandry](https://discuss.elastic.co/u/jandry)\
**Post date:** [November 6, 2023, 3:27pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/2 "2023-11-06T15:27:02Z")

</div>

Additional forgotten informatio: with the agent upgrade, we also upgraded the JVM  
from  
Temurin-17.0.7+7  
to  
Temurin-17.0.9+9

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [November 6, 2023, 3:54pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/3 "2023-11-06T15:54:59Z")

</div>

Hi !

I just tested your configuration with a recent agent version (close to1.43) and the same stack version and did not manage to reproduce the issue.

Can you query the documents in Discover that match `processor.event:"metric"` ?  
This should normally return the metric documents captured by the agent.

---

<div class="post-metadata">

**Author:** ![jandry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jandry/32/126754_2.png) [@jandry](https://discuss.elastic.co/u/jandry)\
**Post date:** [November 7, 2023, 8:56am UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/4 "2023-11-07T08:56:22Z")

</div>

Yes we have metrics

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/6/b602397abbeaab56827913b9c0ab0474f878fcf0.png)

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [November 7, 2023, 10:08am UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/5 "2023-11-07T10:08:47Z")

</div>

I think the problem here is that your metrics are stored with the wrong name, they should have dots `.` and not underscores `_` as separators, which explains why the UI can't display them.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/0/d0042bda94c6e63f6daf1d447af87b8f1833666e.png)

Do you have any custom ingest pipeline that would change the shape of metrics documents ?

---

<div class="post-metadata">

**Author:** ![jandry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jandry/32/126754_2.png) [@jandry](https://discuss.elastic.co/u/jandry)\
**Post date:** [November 7, 2023, 3:49pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/6 "2023-11-07T15:49:42Z")

</div>

No sorry I don't know why it was "." on ly screenshot, but it's "\_"

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/6/46a00c2fa3f0be176c5f02ea326bc2f85da21c57.png)

---

<div class="post-metadata">

**Author:** ![jandry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jandry/32/126754_2.png) [@jandry](https://discuss.elastic.co/u/jandry)\
**Post date:** [November 8, 2023, 3:41pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/7 "2023-11-08T15:41:14Z")

</div>

We did some tests with other APM version for exemple 1.42.0 (same JVM) and we still have the issue with JVM metrics

But when coming back to 1.38 we have the JVM metric but we lost the transactions metrics from spring boot

Thier is certainly some additional settings that was introduce after 1.38 to have those jvm metrics in the tab

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [November 9, 2023, 12:46pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/8 "2023-11-09T12:46:24Z")

</div>

There is an option in the agent that was introduced in an earlier version: `dedot_custom_metrics`, but it only impacts the "custom" metrics that are recorded through the Micrometer or OpenTelemetry APIs, it is not used for the JVM metrics so it's not related to your issue here.

Could you also provide your agent effective configuration (which is within the first lines of the agent log output) ?

I think here it might be a case where it would help to capture the data sent by the agent to the APM server.  
Could you follow the [capture agent debug logs procedure](https://www.elastic.co/guide/en/apm/agent/java/current/trouble-shooting.html#trouble-shooting-logging-procedure) with `log_level=trace` ?

Given the agent sends metrics quite quickly after starting, you only need to capture those verbose logs for a few minutes after startup, then you should be able to inspect those logs and grep them with a grep/regex like `jvm.memory.used` which should match both dots and underscore variants.

With that, we should be able to know if the agent properly captures the metrics as expected or any difference with a previous version.

---

<div class="post-metadata">

**Author:** ![jandry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jandry/32/126754_2.png) [@jandry](https://discuss.elastic.co/u/jandry)\
**Post date:** [November 10, 2023, 2:24pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/9 "2023-11-10T14:24:52Z")

</div>

```auto
2023-11-10 13:27:51,823 [main] DEBUG co.elastic.apm.agent.configuration.StartupInfo - VM Arguments: [-Djava.awt.headless=true, -Djava.security.egd=file:/dev/./urandom, -Dcom.sun.management.jmxremote=true, -Dcom.sun.management.jmxremote.ssl=false, -Dcom.sun.management.jmxremote.authenticate=false, -Dcom.sun.management.jmxremote.port=5000, -Djava.rmi.server.hostname=127.0.0.1, -Dcom.sun.management.jmxremote.host=127.0.0.1, -Dcom.sun.management.jmxremote.rmi.port=5000, -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=127.0.0.1:8000, -Xms2048m, -Xmx10595m, -XX:+AlwaysPreTouch, -XX:+UseStringDeduplication, -Dlogging.config=/opt/xxx/logback-spring.xml, -XX:+AlwaysPreTouch, -javaagent:/opt/apm/elastic-apm-agent-1.43.0.jar]
2023-11-10 13:27:51,824 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - service_name: 'load-test2' (source: Environment Variables)
2023-11-10 13:27:51,824 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - service_node_name: 'xxx.stg.xxx.xxx.company.com' (source: Environment Variables)
2023-11-10 13:27:51,824 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - environment: 'staging' (source: Environment Variables)
2023-11-10 13:27:51,825 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - transaction_sample_rate: '0.5' (source: Environment Variables)
2023-11-10 13:27:51,825 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - transaction_max_spans: '250' (source: Environment Variables)
2023-11-10 13:27:51,825 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - capture_body: 'ERRORS' (source: Environment Variables)
2023-11-10 13:27:51,826 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - trace_methods_duration_threshold: '100ms' (source: Environment Variables)
2023-11-10 13:27:51,826 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - central_config: 'false' (source: Environment Variables)
2023-11-10 13:27:51,826 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - server_urls: 'http://server:8200,http://server:8200,http://server:8200,http://server:8200' (source: Environment Variables)
2023-11-10 13:27:51,827 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - max_queue_size: '4096' (source: Environment Variables)
2023-11-10 13:27:51,827 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - api_request_size: '1mb' (source: Environment Variables)
2023-11-10 13:27:51,827 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - application_packages: 'com.xxx,com.xxx' (source: Environment Variables)
2023-11-10 13:27:51,828 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - span_frames_min_duration: '25ms' (source: Environment Variables)
2023-11-10 13:27:51,828 [main] WARN co.elastic.apm.agent.configuration.StartupInfo - Detected usage of deprecated configuration option 'span_frames_min_duration'. This option might be removed in the future. Please refer to the documentation about alternatives.
2023-11-10 13:27:51,828 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - log_level: 'TRACE' (source: Environment Variables)
2023-11-10 13:27:51,829 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - log_file: '/var/log/instance/xxx/elastic-apm.log' (source: Environment Variables)

```

---

<div class="post-metadata">

**Author:** ![jandry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jandry/32/126754_2.png) [@jandry](https://discuss.elastic.co/u/jandry)\
**Post date:** [November 10, 2023, 2:25pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/10 "2023-11-10T14:25:09Z")

</div>

```auto
{"metricset":{"timestamp":1699614245380000,"tags":{"area":"heap","id":"G1 Survivor Space"},"samples":{"jvm_memory_used":{"value":38749096.0},"jvm_memory_committed":{"value":41943040.0},"jvm_memory_max":{"value":-1.0}}}}
{"metricset":{"timestamp":1699614245380000,"tags":{"area":"nonheap","id":"Compressed Class Space"},"samples":{"jvm_memory_max":{"value":1073741824.0},"jvm_memory_used":{"value":28004416.0},"jvm_memory_committed":{"value":29032448.0}}}}
{"metricset":{"timestamp":1699614245380000,"tags":{"area":"nonheap","id":"CodeHeap 'profiled nmethods'"},"samples":{"jvm_memory_used":{"value":39452800.0},"jvm_memory_committed":{"value":39518208.0},"jvm_memory_max":{"value":122912768.0}}}}
{"metricset":{"timestamp":1699614245380000,"tags":{"area":"nonheap","id":"Metaspace"},"samples":{"jvm_memory_used":{"value":227871520.0},"jvm_memory_committed":{"value":229703680.0},"jvm_memory_max":{"value":-1.0}}}}
{"metricset":{"timestamp":1699614245380000,"tags":{"area":"nonheap","id":"CodeHeap 'non-nmethods'"},"samples":{"jvm_memory_max":{"value":5828608.0},"jvm_memory_used":{"value":2755968.0},"jvm_memory_committed":{"value":2883584.0}}}}
{"metricset":{"timestamp":1699614245380000,"tags":{"area":"heap","id":"G1 Eden Space"},"samples":{"jvm_memory_max":{"value":-1.0},"jvm_memory_committed":{"value":553648128.0},"jvm_memory_used":{"value":260046848.0}}}}
{"metricset":{"timestamp":1699614245380000,"tags":{"area":"heap","id":"G1 Old Gen"},"samples":{"jvm_memory_used":{"value":1245626368.0},"jvm_memory_committed":{"value":5016387584.0},"jvm_memory_max":{"value":11114905600.0}}}}
{"metricset":{"timestamp":1699614245380000,"tags":{"area":"nonheap","id":"CodeHeap 'non-profiled nmethods'"},"samples":{"jvm_memory_committed":{"value":17694720.0},"jvm_memory_used":{"value":17262848.0},"jvm_memory_max":{"value":122916864.0}}}}
{"metricset":{"timestamp":1699614275380000,"tags":{"area":"heap","id":"G1 Survivor Space"},"samples":{"jvm_memory_used":{"value":18618280.0},"jvm_memory_committed":{"value":25165824.0},"jvm_memory_max":{"value":-1.0}}}}
{"metricset":{"timestamp":1699614275380000,"tags":{"area":"nonheap","id":"Compressed Class Space"},"samples":{"jvm_memory_max":{"value":1073741824.0},"jvm_memory_used":{"value":29586880.0},"jvm_memory_committed":{"value":30605312.0}}}}
{"metricset":{"timestamp":1699614275380000,"tags":{"area":"nonheap","id":"CodeHeap 'profiled nmethods'"},"samples":{"jvm_memory_used":{"value":41390976.0},"jvm_memory_committed":{"value":41418752.0},"jvm_memory_max":{"value":122912768.0}}}}
{"metricset":{"timestamp":1699614275380000,"tags":{"area":"nonheap","id":"Metaspace"},"samples":{"jvm_memory_used":{"value":239819704.0},"jvm_memory_committed":{"value":241696768.0},"jvm_memory_max":{"value":-1.0}}}}
{"metricset":{"timestamp":1699614275380000,"tags":{"area":"nonheap","id":"CodeHeap 'non-nmethods'"},"samples":{"jvm_memory_max":{"value":5828608.0},"jvm_memory_used":{"value":2810752.0},"jvm_memory_committed":{"value":2949120.0}}}}
{"metricset":{"timestamp":1699614275380000,"tags":{"area":"heap","id":"G1 Eden Space"},"samples":{"jvm_memory_max":{"value":-1.0},"jvm_memory_committed":{"value":1493172224.0},"jvm_memory_used":{"value":1015021568.0}}}}
{"metricset":{"timestamp":1699614275380000,"tags":{"area":"heap","id":"G1 Old Gen"},"samples":{"jvm_memory_used":{"value":1279709696.0},"jvm_memory_committed":{"value":4093640704.0},"jvm_memory_max":{"value":11114905600.0}}}}
{"metricset":{"timestamp":1699614275380000,"tags":{"area":"nonheap","id":"CodeHeap 'non-profiled nmethods'"},"samples":{"jvm_memory_committed":{"value":18939904.0},"jvm_memory_used":{"value":18903808.0},"jvm_memory_max":{"value":122916864.0}}}}

```

---

<div class="post-metadata">

**Author:** ![jandry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jandry/32/126754_2.png) [@jandry](https://discuss.elastic.co/u/jandry)\
**Post date:** [November 10, 2023, 2:25pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/11 "2023-11-10T14:25:27Z")

</div>

Please find what you ask above. Thanks

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [November 10, 2023, 4:23pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/12 "2023-11-10T16:23:49Z")

</div>

Thanks, that confirms that the problem is on the agent side.  
I need to investigate this further on my side to understand how this could happen.

There is nothing obviously wrong in your agent configuration, which means it could be a bug in the agent.

---

<div class="post-metadata">

**Author:** ![jandry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jandry/32/126754_2.png) [@jandry](https://discuss.elastic.co/u/jandry)\
**Post date:** [November 10, 2023, 4:35pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/13 "2023-11-10T16:35:14Z")

</div>

☹ thanks for the first response

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [November 13, 2023, 4:59pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/14 "2023-11-13T16:59:20Z")

</div>

In your configuration, there is something quite odd but probably not related to the issue, the value for `server_url` is duplicated (set in the `ELASTIC_APM_SERVER_URLS` environment variable in your case).

> [@jandry](#):
>
> `server_urls: 'http://server:8200,http://server:8200,http://server:8200,http://server:8200'`

Do you use OpenTelemetry or Micrometer APIs to capture metrics in your application ?

Also, does the `capture_jmx_metrics` is configured ? From the provided agent logs it does not seem set, but worth double-checking anyway.

---

<div class="post-metadata">

**Author:** ![jandry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jandry/32/126754_2.png) [@jandry](https://discuss.elastic.co/u/jandry)\
**Post date:** [November 14, 2023, 3:24pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/15 "2023-11-14T15:24:29Z")

</div>

Hello,  
For `ELASTIC_APM_SERVER_URLS` it's just our obfuscation: wa masked the differents url but we same "token": server instead of using diffrent tokens server1, server2...

We don't use OpenTelemetry for the moment. We are starting a POC on it

To our knowledge except if it's a default value, we never set 'capture\_jmx\_metrics' in our override.apm.conf

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [November 15, 2023, 5:42pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/16 "2023-11-15T17:42:51Z")

</div>

Actually, by checking more closely the list of metrics that you've sent those might not be all captured by the agent auto-instrumentation, especially if your application is using micrometer.

Could you try to disable the micrometer instrumentation by setting `disable_instrumentations=micrometer` ([doc](https://www.elastic.co/guide/en/apm/agent/java/current/config-core.html#config-disable-instrumentations)) ?

With that, the metrics that you have only metrics that are captured by default by the agent, which are the ones that have dots `.` in their name, like `jvm.fd.used`.

If that solves the issue, we still need to investigate how it could interfere (or overwrite) the default agent metrics, but at least it should help us make some progress on this problem.

Also, would it be possible to double check if some of the jvm metrics have a dot in their name ? for example searching for `jvm.fd.used` would be relevant.

---

<div class="post-metadata">

**Author:** ![jandry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jandry/32/126754_2.png) [@jandry](https://discuss.elastic.co/u/jandry)\
**Post date:** [November 16, 2023, 11:30am UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/17 "2023-11-16T11:30:20Z")

</div>

Hi  
Please find our answers:

We added ELASTIC\_APM\_DISABLE\_INSTRUMENTATIONS=micrometer to our configuration.

In the logs we have:

2023-11-16 10:57:48,278 [main] INFO co.elastic.apm.agent.configuration.StartupInfo - disable\_instrumentations: 'micrometer' (source: Environment Variables)

But, it didn't fix the issue. JVMs are still not displayed.

For the second part (JVM metrics with a dot in their name):

> {"metricset":{"timestamp":1700133015061000,"samples":{"system.process.cpu.total.norm.pct":{"value":0.9686509921627481},"jvm.memory.heap.used":{"value":221369568.0},"jvm.memory.non\_heap.used":{"value":128880536.0},"jvm.memory.heap.max":{"value":11114905600.0},"jvm.fd.used":{"value":159.0},"jvm.gc.alloc":{"value":4706838512.0},"jvm.memory.non\_heap.committed":{"value":130613248.0},"system.cpu.total.norm.pct":{"value":0.991829247957312},"system.process.cgroup.memory.mem.usage.bytes":{"value":2474967040.0},"system.process.memory.size":{"value":14271287296.0},"jvm.memory.heap.committed":{"value":2147483648.0},"system.memory.actual.free":{"value":12541489152.0},"jvm.fd.max":{"value":524288.0},"system.memory.total":{"value":16479371264.0},"jvm.thread.count":{"value":22.0}}}}

Thanks

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [November 16, 2023, 2:47pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/18 "2023-11-16T14:47:13Z")

</div>

Ok then it means that unlike what I initially thought, the JVM metrics are very probably correctly captured by the agent, I was misled by the metrics with `_` in their name that are actually created by micrometer.

Given you miss only the metrics part, I think it could also be related to missing `metadata` attributes, and in order to investigate that I'll need a complete JSON document of one of those metrics. For example. by filtering with `jvm.memory.heap.used>0` in Discover, you can alter the values for obfuscation, but should not remove anything from the document structure.

---

<div class="post-metadata">

**Author:** ![jandry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jandry/32/126754_2.png) [@jandry](https://discuss.elastic.co/u/jandry)\
**Post date:** [November 20, 2023, 1:30pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/19 "2023-11-20T13:30:23Z")

</div>

jvm.memory.heap.used is empty with this agent version

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/0/805965239cd444719b22d15e6933c58d001ed0e2.png)

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [November 20, 2023, 2:15pm UTC](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537/20 "2023-11-20T14:15:14Z")

</div>

Does this query return anything with the previous agent version ?

If yes, then please provide:

- one document for the old agent that works
- one document for the new agent that does not work (just filtering on the agent version should be enough).

[Next page](https://discuss.elastic.co/t/no-jvms-were-found-in-jvm-tab-after-apm-upgrade-from-1-38-to-1-43/346537.md?page=2)