# Ignition JVM Application Monitoring

**URL:** <https://forum.inductiveautomation.com/t/ignition-jvm-application-monitoring/69727>\
**Category:** Ignition\
**Created:** [February 11, 2023, 3:09am UTC](https://forum.inductiveautomation.com/t/ignition-jvm-application-monitoring/69727 "2023-02-11T03:09:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 11, 2023, 4:11am UTC](https://forum.inductiveautomation.com/t/ignition-jvm-application-monitoring/69727/2 "2023-02-11T04:11:09Z")

</div>

I've been using VisualVM, making remote JMX connections to my Ignition instances. The ability to easily diff snapshots then drill down into heap dumps has been very helpful.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-jvm-application-monitoring/69727)._