---
title: JMX monitoring
description: This functionality is deprecated.
component: pingam
version: 8.1
page_id: pingam:monitoring:monitoring-jmx
canonical_url: https://docs.pingidentity.com/pingam/8.1/monitoring/monitoring-jmx.html
keywords: ["Monitoring"]
page_aliases: ["maintenance-guide:monitoring-jmx.adoc", "monitoring-guide:monitoring-jmx.adoc"]
---

# JMX monitoring

|   |                                                                                                                            |
| - | -------------------------------------------------------------------------------------------------------------------------- |
|   | This functionality is [deprecated](https://docs.pingidentity.com/pingam/release-notes/stability.html#interface-stability). |

You can configure AM to let you listen for Java Management Extension (JMX) clients, by default on port 9999. Go to Configure > Global Services > Monitoring in the AM admin UI and make sure both Monitoring Status and Monitoring RMI interface status are enabled.

A number of tools support JMX, including `jvisualvm` and `jconsole`. When you use `jconsole` to browse AM MBeans for example, the default URL for the AM running on the local system is `service:jmx:rmi:///jndi/rmi://localhost:9999/server`.

```bash
$ jconsole service:jmx:rmi:///jndi/rmi://localhost:9999/server &
```

To browse MBeans, connect to your web application container, and go to the AM MBeans. By default, JMX monitoring for the container is likely to be accessible only locally, using the process ID.

![You can monitor an instance over JMX.](_images/jconsole-to-openam.png)Figure 1. JConsole browsing MBeans

Also refer to [Monitoring and Management Using JMX Technology](https://docs.oracle.com/en/java/javase/25/management/monitoring-and-management-using-jmx-technology.html) for instructions on how to connect remotely, how to use SSL, and so on.

|   |                                                                                                                                                                                                                                                                |
| - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | JMX has a limitation in that some Operations and CTS tables cannot be properly serialized from AM to JMX. As a result, only a portion of AM's monitoring information is available through JMX.Use Prometheus, Graphite, or common REST monitoring if possible. |

For monitoring metrics reference, refer to [Monitoring metrics](monitoring-metrics.html).