- 2 minutes to read
JMX Monitoring Agent - Troubleshooting and FAQ
This troubleshooting guide answers common questions about configuring and operating the Nodinite JMX Monitoring Agent. The agent monitors two values per JVM, CPU usage and free heap memory, and shows a JVM it can't reach as Unavailable. Select a topic below to find targeted guidance.
Topics cover heap memory, CPU usage, garbage collection, Docker and Kubernetes deployments, polling frequency, environment thresholds, remote monitoring, multi-JVM setups, OS monitoring, and thread deadlocks.
Troubleshooting Topics
- Heap Used vs Committed — Heap used, committed, and max, and how the agent uses free heap
- Supported Garbage Collectors — How each garbage collector shapes free heap, and Heap Size thresholds per collector
- Correlate Heap Spikes — How to correlate heap memory spikes with application events
- Environment-Specific Thresholds — Configure different warning and error thresholds per environment
- Polling Frequency — How polling frequency and Duration affect alert latency
- Multi-JVM Monitoring — Monitor multiple JVM instances from a single agent
- OS vs JVM Monitoring — What the JMX agent covers and what OS monitoring covers
- Docker Container Monitoring — Monitor JVMs running inside Docker containers
- Enable JMX Remote Monitoring — Enable JMX remote monitoring in your JVM applications
- Costs and Licensing — Licensing costs and open-source component details
- Supported Java Versions — Which Java versions and JDK distributions are compatible with the agent
- Thread Deadlock Detection — The agent doesn't detect thread deadlocks; how to find them with JVM tools
Next Steps
Prerequisites
Install JMX Monitoring Agent