Documentation forAppOptics

Runtime metrics (legacy agent)

The following content pertains to runtime metrics for the legacy AppOptics Java Agent.

AppOptics agents are no long receiving updates. The new SolarWinds Observability libraries can send APM data in AppOptics and are regularly updated with new features and improvements. If you are still relying on the AppOptics agents and your components are supported by the new libraries, consider transitioning to the SolarWinds Observability libraries for your APM needs. For more information about the benefits of migrating to the SolarWinds Observability libraries. Alternatively, you can use SolarWinds Observability as your primary APM solution.

If you have already transitioned to the new SolarWinds Observability Java Library, see the SolarWinds Java Library documentation for runtime metrics information.

SolarWinds Observability libraries are not compatible with AppOptics agents. Do not use a mix of SolarWinds Observability libraries and AppOptics agents to instrument applications that are part of a distributed trace.

Java runtime metrics are gathered from JMX MBeans and reported by the agent on interval. Reporting is enabled by default for the metrics described below. To disable reporting or enable additional JMX metrics please refer to Java JMX configuration.

Metric Description
trace.jvm.GarbageCollector.* JVM Garbage collection cumulative values, plotted as derivatives in the JMX dashboard
trace.jvm.Memory.* Heap and non-heap memory details
trace.jvm.MemoryPool.* Memory pool details. A memory pool represents the memory resource managed by the JVM, for example Metaspace(PermGen)
trace.jvm.OperatingSystem.* Operating system details such as process CPU load
trace.jvm.Runtime.* Java process uptime
trace.jvm.Threading.* Thread details such as thread count