Discussion Feed

When configuring a Java agent to monitor a Spring Boot application, you need to configure the Java agent parameter before the Spring Boot application jar file.    Example:  java -javaagent:<agent-install-dir>/ver4.x.x/javaagent.jar -jar application.jar       ... View more

Issue  On some of your JVM environments, Garbage Collection (GC) metrics are not reporting out of the box.   Observations The agent collects and reports the GC metrics based on the related MBeans exposed by the underlying JVM. If the JVM does not return the related Mbeans, then GC metrics will not be reported by the agent.   In this case, the agent logs will report the messages below:  [Thread-0] 06 Feb 2018 07:06:23,529 WARN MemoryMetricGenerator - Current JVM GC MX Beans - GPGC New, GPGC Old, not registered with JMX Service.Please add the appropriate minor collection bean name to JMX Service property key name : jmx-gc-minorCollectionBean [Thread-0] 06 Feb 2018 07:06:23,529 WARN MemoryMetricGenerator - Current JVM GC MX Beans - GPGC New, GPGC Old, not registered with JMX Service.Please add the appropriate major collection bean name to JMX Service property key name : jmx-gc-minorCollectionBean   Solution 1 You will need to analyze the GC mechanisms used by the JVM by verifying with JConsole or any other JMX tool. Refer to the attached screenshots for an example.    Identify the GC mechanism and configure it in the " app-agent-config.xml " file under "JMXService" configurations.   Example: <agent-service name="JMXService" enabled="true"> <configuration-properties> <property name="jmx-gc-minorCollectionBean" value="PS MarkSweep"/> <property name="jmx-gc-majorCollectionBean" value="PS MarkSweep"/> <property name="jmx-server-metrics-update-interval-in-seconds" value="60"/> </configuration-properties>   Restart the JVM for the changes to take effect.   Solution 2 You can create custom JMX metrics as follows, although you may need to use the JMX browser to confirm the exact names.   Minor Collection Major Collection   ... View more

Issue Business transactions are being marked as errors, but the error details are not showing on transaction snapshots.   Observation This could be due to the error registration limit on the agent side. In the agent logs, you may see this message: INFO ErrorRegistry - ErrorRegistry ADD registration limit has been reached, dropping error object   Resolution If you see this error, you will need to register the node property below and set the value to >500. Node Property : max-error-add-registration-limit Type : Int Value : 500 (default) ... View more