# Kibana failed to view apm Jvm Heap memory pools metrics

**URL:** https://discuss.elastic.co/t/kibana-failed-to-view-apm-jvm-heap-memory-pools-metrics/366768
**Category:** Elastic Observability
**Created:** [September 19, 2024, 6:41am UTC](https://discuss.elastic.co/t/kibana-failed-to-view-apm-jvm-heap-memory-pools-metrics/366768 "2024-09-19T06:41:51Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![arT1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/art1/32/137703_2.png) [@arT1](https://discuss.elastic.co/u/arT1)
#### Post date: [September 19, 2024, 6:41am UTC](https://discuss.elastic.co/t/kibana-failed-to-view-apm-jvm-heap-memory-pools-metrics/366768/1 "2024-09-19T06:41:51Z")

</div>

Versions: 版本：

- ES v8.13.3
- Kibana v8.13.3
- apm-server v8.13.3
- apm-agent v1.51.0

I couldn't see Heap memory pools in JVM metrics when I was testing APM server. Kibana shows that only the reduced time range can be used for the specified default time field on the data view. Use a different view of the data with a default time field, or remove the reduced time range from Committed [bytes].

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

---

<div class="post-metadata">

### Author: ![arT1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/art1/32/137703_2.png) [@arT1](https://discuss.elastic.co/u/arT1)
#### Post date: [September 19, 2024, 6:51am UTC](https://discuss.elastic.co/t/kibana-failed-to-view-apm-jvm-heap-memory-pools-metrics/366768/2 "2024-09-19T06:51:45Z")

</div>

I queried for the apm\* index data and found that the metric data exists

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