Java Agent Troubleshooting Framework Configuration

Java Agent Troubleshooting Framework

If you are not seeing any data from your Java application you should first follow our Java Agent Install troubleshooting guide this guide assumes you are seeing data but it isn’t looking like what you expected. it will run you through a number of common configuration changes that may resolve the issue.

Missing Application

If you see no application or the application is there and there is no data at all, see Java Agent Install troubleshooting guide

Note: If the agent successfully creates an agent log and is adding information to the log, search the logs for “Reporting to” as the results should give the URL to the application. If it is reporting to the wrong account, the license key needs to be corrected.

Check for applications named “My Application”. This is the default value for the app_name configuration option. Edit the newrelic.yml file located near the newrelic.jar and update the app_name value to the desired application name.

See https://docs.newrelic.com/docs/agents/manage-apm-agents/app-naming/name-your-application

https://docs.newrelic.com/docs/agents/java-agent/configuration/name-your-java-application

Hosts or JVM instances are not named as expected

If running multiple JVM instances on the same host with the same port and they are rolled up together, use appserver_port to differentiate the JVMs

See https://docs.newrelic.com/docs/agents/java-agent/configuration/hostname-logic-java

And https://docs.newrelic.com/docs/agents/java-agent/troubleshooting/host-links-missing-java-apps-apm-summary

Missing Transactions

See Transaction naming protocol

  1. If there are no transactions showing on the Summary, check the JVMs dashboard for information on Heap Memory and GC. JVM health metrics gathered by querying the JMX should be the basic information collected from the JVM the agent is running within.

  2. Out-of-the-box instrumentation is available for technology on the Compatibility and requirements for the Java agent

  3. Additional instrumentation (Experimental) modules - Extension and additional instrumentation modules

  4. Verbose agent logging will show what the agent sees and how it handles transaction activity. Use Generate debug logs for troubleshooting (Java) to gather the logging information.

  5. It may be necessary to raise visibility of the calls to methods or classes for the agent using Java custom instrumentation

    1. Custom Instrumentation Editor - UI option Custom instrumentation editor: Instrument from UI
    2. Via XML - Java instrumentation by XML
    3. Annotation via API - Java agent API: Instrument using annotation

Missing segments (External Calls, Database calls) (Regular or Cross-Application Tracing)

Check for the use of async patterns and review this documentation - Introduction to Java async instrumentation