• EnglishEspañol日本語한국어Português
  • 로그인지금 시작하기

Java agent v7.10.0

September 15, 2022Download
Download this agent version

New features and improvements

Added the following Jakarta EE 9/9.1 compatible instrumentation:

  • Jetty 11
  • Tomcat 10
  • Enterprise Java Beans 4.0
  • Jakarta RS/WS
  • Jersey 3+
  • Jersey Client 3
  • JSP 3
  • Servlet 5 & 6
  • Jakarata.xml
  • JMS 3
  • Glassfish 6.0
  • Open Liberty

Code level metrics

For traced methods in automatic instrumentation or from @Trace annotations, the agent is now capable of reporting metrics with method-level granularity. When the new functionality is enabled, the agent will associate source-code-related metadata with some metrics. Then, when the corresponding Java class file that defines the methods is loaded up in a New Relic CodeStream-powered IDE, the four golden signals for each method will be presented to the developer directly.

Agent log forwarding now adds the following attributes to log events for the log4j2 and logback1.2 frameworks:

  • thread.name
  • thread.id
  • logger.name
  • logger.fqcn
  • error.class
  • error.stack
  • error.message


Fixed an issue with distributed tracing headers not being added on external requests made with the HttpUrlConnection client

Support statement

New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

Full changelog: https://github.com/newrelic/newrelic-java-agent/compare/v7.9.0...v7.10.0

Update to latest version

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

  1. Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
  2. Download the agent.
  3. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
  4. Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
  5. Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences

We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings.

For example, if you diff the default newrelic.yml files for Java agent versions 7.7.0 and 7.8.0, the results printed to the console will be:

➜ diff newrelic_7.7.0.yml newrelic_7.8.0.yml
< #forwarding:
> forwarding:
< # When true, application logs will be forwarded to New Relic. The default is false.
< #enabled: false
> # When true, application logs will be forwarded to New Relic. The default is true.
> enabled: true

In this example, these lines were added to the default newrelic.yml in Java agent version 7.8.0. If you are moving to 7.8.0 or higher, you should add these new lines to your original newrelic.yml.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.