- 1 minutes to read
JMX Monitoring Agent - Troubleshooting and FAQ
This troubleshooting guide answers common questions about configuring and operating the Nodinite JMX Monitoring Agent. 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, and OS monitoring.
Troubleshooting Topics
- Heap Used vs Committed — Understand the difference between heap used and committed memory metrics
- Supported Garbage Collectors — Which JVM garbage collectors are supported and how they affect monitoring
- 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 — Configure how often the agent collects JVM metrics
- Multi-JVM Monitoring — Monitor multiple JVM instances from a single agent
- OS vs JVM Monitoring — Understand the difference between OS-level and JVM-level monitoring
- 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 — Detect and resolve thread deadlocks in monitored JVM applications
Next Step
Prerequisites
Install JMX Monitoring Agent