# APM Dashboard Showing Unrealistic Memory Allocation (1EB/m) **URL:** \ **Category:** APM\ **Tags:** docker, java\ **Created:** [October 30, 2024, 6:49pm UTC](https://discuss.elastic.co/t/apm-dashboard-showing-unrealistic-memory-allocation-1eb-m/369841 "2024-10-30T18:49:58Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![sto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sto/32/138876_2.png) [@sto](https://discuss.elastic.co/u/sto)\ **Post date:** [October 30, 2024, 6:49pm UTC](https://discuss.elastic.co/t/apm-dashboard-showing-unrealistic-memory-allocation-1eb-m/369841/1 "2024-10-30T18:49:58Z")
We’re running a Spring Boot application on Java 8 with the latest APM Java Agent (v1.52.0) and Elasticsearch 8.13.4. Despite following the setup instructions, the APM dashboard shows a **memory peak of 1EB/m (exabytes per minute)**, as seen in the attached screenshot—clearly an impossible value for our setup. There’s a load balancer in front of the APM servers, and we haven’t made any changes to index patterns or agent configurations. Any idea what could be causing this? Could it be a configuration issue or a bug? We’d appreciate any advice on how to debug this! Logs and additional info available if needed. ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/c/bc08fda3e616fc4ef4b04de67f3d06ac04645086.jpeg) ---
**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\ **Post date:** [October 30, 2024, 7:43pm UTC](https://discuss.elastic.co/t/apm-dashboard-showing-unrealistic-memory-allocation-1eb-m/369841/2 "2024-10-30T19:43:15Z")
Is this aggregating values from multiple instances? ---
**Author:** ![sto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sto/32/138876_2.png) [@sto](https://discuss.elastic.co/u/sto)\ **Post date:** [October 30, 2024, 10:53pm UTC](https://discuss.elastic.co/t/apm-dashboard-showing-unrealistic-memory-allocation-1eb-m/369841/3 "2024-10-30T22:53:52Z")
> [@Jack\_Shirazi](#): > > Is this aggregating values from multiple instances? Yes, it aggregates values from multiple pods, and that seems to be the issue. When filtering a single node, the metrics appear empty for each one. However, when aggregating two or more nodes, the metrics start showing unrealistic values. Could this be a bug in Kibana? ---
**Author:** ![Jack\_Shirazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_shirazi/32/91641_2.png) [@Jack\_Shirazi](https://discuss.elastic.co/u/Jack_Shirazi)\ **Post date:** [October 31, 2024, 4:40pm UTC](https://discuss.elastic.co/t/apm-dashboard-showing-unrealistic-memory-allocation-1eb-m/369841/4 "2024-10-31T16:40:00Z")
You can look at the underlying documents (eg in discover or directly querying ES), take that (or any) time sample, and see if it's incorrectly aggregating or whether you have some burst of instances and/or allocations