# JVM Status and Memory leak

**URL:** <https://community.dynatrace.com/t/jvm-status-and-memory-leak/52239>\
**Category:** Open Q&A\
**Tags:** dynatrace-managed, services, oneagent, processes\
**Created:** [June 25, 2025, 7:37pm UTC](https://community.dynatrace.com/t/jvm-status-and-memory-leak/52239 "2025-06-25T19:37:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vikas\_g1997](https://avatars.discourse-cdn.com/v4/letter/v/b3f665/32.png) [@Vikas\_g1997](https://community.dynatrace.com/u/Vikas_g1997)\
**Post date:** [June 25, 2025, 7:37pm UTC](https://community.dynatrace.com/t/jvm-status-and-memory-leak/52239/1 "2025-06-25T19:37:13Z")

</div>

Hi Team,

For a more detailed analysis of JVMs, could anyone suggest how we can set up alerts for JVM status and detect potential memory leaks? Currently, we do not have any built-in metrics for this.

Is it possible to visualize this data on a dashboard or create alerts using JMX plugins?

 ![Vikas_g1997_0-1750880202659.png](https://global.discourse-cdn.com/dynatrace/original/3X/5/0/5004b87992db9f707ea0a522ffc448ad4d58d513.png)

---

<div class="post-metadata">

**Author:** ![lubrman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/lubrman/32/7353_2.png) [@lubrman](https://community.dynatrace.com/u/lubrman)\
**Post date:** [June 26, 2025, 7:05am UTC](https://community.dynatrace.com/t/jvm-status-and-memory-leak/52239/2 "2025-06-26T07:05:02Z")

</div>

Hi&nbsp;[@Vikas\_g1997](https://community.dynatrace.com/user/57336)

 ![lubrman_0-1750920694613.png](https://global.discourse-cdn.com/dynatrace/original/3X/b/8/b8611fc11f391a72fceaf6ca59f2567c83c6586e.png)

Yes, displaying this in Dynatrace is of course possible — the basic view is available under the JVM tab on the detected process. Dynatrace itself natively alerts on certain GC warnings, such as long-term GC and similar events. However, the threshold is auto-adaptive, so if you want something more static, I recommend setting up a metric event based on the metrics provided by OneAgent during measurement. You can find these metrics under “JVM” in the Metrics section.

 ![lubrman_2-1750920885614.png](https://global.discourse-cdn.com/dynatrace/original/3X/1/9/196489a71858a2f2b293d96f943be7f88929cefa.png)

You can take inspiration from our metric, which measures memory usage, for example — it monitors memory utilization.  
((builtin:tech.jvm.memory.pool.used:filter(and(or(in(“dt.entity.process\_group\_instance”,entitySelector(“type(process\_group\_instance),tag(~”[Environment]DT\_RELEASE\_PRODUCT:Your tag~“),tag(~”[Environment]DT\_RELEASE\_STAGE:Your tag~“)”))))):splitBy():sort(value(auto,descending))/(builtin:tech.jvm.memory.pool.max:filter(and(or(in(“dt.entity.process\_group\_instance”,entitySelector(“type(process\_group\_instance),tag(~”[Environment]DT\_RELEASE\_PRODUCT:Your tag~“),tag(~”[Environment]DT\_RELEASE\_STAGE:Your tag~“)”))))):splitBy():max:sort(value(max,descending)))))\*100

Alternatively, you can display the data on a similar dashboard.

 ![lubrman_3-1750921271847.png](https://global.discourse-cdn.com/dynatrace/original/3X/4/9/49de7a5b6e18a9f640f96739b5047edd67b9d921.png)

Here are some example metrics for reference  
builtin:tech.generic.mem.workingSetSize  
builtin:tech.jvm.memory.pool.committed&nbsp; poolname: metaspace  
builtin:tech.jvm.memory.pool.committed&nbsp;&nbsp;poolname: CodeHeap 'profiled nmethods
