JVM metrics page

You can use New Relic's Java agent to collect and view additional metrics provided by the most common application servers via JMX. The collected metrics vary by application server and include measurements of thread pools, HTTP sessions, and transactions.

Access to this feature depends on your subscription level.

Viewing JVM metrics

Application servers collect and report different metrics which appear on New Relic APM's JVM page. At a minimum, each application server collects and reports metric data on memory. For instructions on enabling JMX metrics, refer to your application server's documentation.

For applications using New Relic via Heroku, the JVM page is named Instances.

To view JVM metrics:

  1. From rpm.newrelic.com. select APM > (selected app) > Monitoring > JVMs > (selected JVM).
  2. From the selected JVM's Memory page, use any of New Relic's standard user interface functions to drill down into detailed information.
  3. To view other metrics, select any available tab.
  4. Optional: To use the thread profiler to look for bottlenecks in data on executing threads, select Profile this JVM.
JVM-new-tabset.png
APM > (selected app) > Monitoring > JVMs: Depending on the metrics your application server is reporting, one or more tabs appear on your JVM page.

Tabs available by app server

The following table lists which tabs appear on the JVM page for application servers. If your application server does not report a particular type of metric data, the tab does not appear on your JVM page.

App Server Memory Thread pools HTTP Sessions App Server Transactions
Glassfish [check] [check] [check] [check]
JBoss 5AS [check] [check] [check]
JBoss 6AS [check] [check] [check]
JBoss 6EAP [check] [check]
JBoss 7AS [check] [check]
Jetty [check] [check]
Resin 3 [check] [check] [check]
Resin 4 [check] [check] [check] [check]
Tomcat [check] [check] [check]
TomEE [check] [check] [check]
WebLogic [check] [check]
Websphere [check] [check] [check]

Metrics available by tab

Here is a summary of the metrics available from the JVM page. If the application server does not support a particular metric, that tab does not appear on your JVM page.

JMX Metric charts
Memory
  • Heap memory usage: The used and committed heap in MB.
  • Non-heap memory pool usage for the JVM: The used code cache and used CMS Perm Gen in MB.
  • Garbage collection: The garbage collection CPU time.
  • Class count: The loaded and unloaded class count for the JVM.
Thread pools
  • Thread count: The current number of active threads in the JVM.
  • Thread pool: The active and idle thread count for the pool. On supported application servers, a chart shows each thread pool present in the application server, as well as the ratio of active to maximum thread count for each thread pool.
HTTP sessions
  • Session: The active, expired, and rejected HTTP session counts for the application. On supported application servers, a chart shows each application present in the application server.
App server transactions
  • Active transaction: The number of active transactions within the application server's transaction manager.
  • Created transaction: The change in the total number of created transactions per application server. Some application servers separate top level transactions and nested transactions.
  • Finished transaction: The change in the total number of finished transactions per application server. Some application servers separate them by aborted and committed completed transactions.

For more help

Additional documentation resources include:

Join the discussion about Java monitoring in the New Relic Online Technical Community! The Technical Community is a public platform to discuss and troubleshoot your New Relic toolset.

If you need additional help, get support at support.newrelic.com.