Resolve metric grouping issues in Java

Problem

Your app uses New Relic's Java agent and you run into a metric grouping issue.

Solution

Try these troubleshooting steps before metric grouping issues become too big of a problem.

Reconfigure the Java agent

By default, the agent names transactions based on your framework and the various components of your application. However, if the Java agent is configured to disable component-based naming, it will be unable to properly name those transactions. This will often lead to a metric grouping issue.

To troubleshoot your Java agent configuration: If component-based naming has been disabled, re-enable it.

Upgrade the Java agent

Some metric grouping issues can be resolved by simply upgrading your New Relic agent. Unless you have a good reason not to, New Relic recommends always upgrading to the most recent version.

To troubleshoot your Java agent version, refer to the Java agent release notes. The release notes summarize fixes and changes, including situations where agent-related metric grouping issues have been corrected.

Manually name transactions

If your Java agent version is up-to-date and correctly configured, but you still run into a metric grouping issue, you may need to manually name your transactions. To help you get started, refer to New Relic's example program using the Java API.

The Java agent API allows you to set a transaction name within your application. This helps eliminate unique names and IDs in metric names.

Resolve metric limit placed by New Relic

After detecting a metric grouping issue, New Relic automatically applies a metric limit to your application. This prevents new metric names from coming into your application.

The metric limit prevents the problem from getting any worse. However, before New Relic can remove the limit, the cause of the metric grouping issue must be resolved.

Once the underlying problem has been managed, New Relic Support will check your application to make sure that:

  • Your upgraded Java agent no longer sends the older metrics that were causing trouble.
  • Your new transaction names properly exclude the unique portions of the name.

After confirming that the metric grouping issue is resolved, New Relic Support will manually update your application so that new metric names will once again be allowed.

For more help

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.