Java agent release notesRSS

New features and improvements

• Add support for Jetty 12, including Jetty’s implementation of the Jakarta EE 8, 9, and 10 specs. 1621
• Add support for Vert.x versions 4.0.0 through 4.4.x 1588
• Add instrumentation for graphql-java 21 1454
• Instrument r2dbc-postgresql 0.9.2 till latest 1413
• Reintroduce the legacy HTTP Attributes that were removed in v8.0.0 to support customers with alerts and dashboards that require them 1671 The attributes are:
• httpResponseCode
• httpResponseMessage
• response.status
• response.statusMessage

Attribute reporting is configurable via the following means.

YAML:

attributes:
  http_attribute_mode: both

System property:

-Dnewrelic.config.attributes.http_attribute_mode=both

Environment variable:

NEW_RELIC_ATTRIBUTES_HTTP_ATTRIBUTE=both

The configuration options are:

• standard : The agent will send new standard attributes. This configuration is recommended but requires that any alerts or dashboards using attributes be updated to use these new attributes. This setting will reduce the amount of ingest used for attribute reporting.

• legacy : The agent will send the legacy attributes referenced above. Customers with alerts or dashboard requiring these attributes can continue to be used as-is. This setting will reduce the amount of ingest used for attribute reporting.

• both : This is the default configuration, the agent will send BOTH legacy AND standard HTTP attributes. This configuration was intended to support customers that are unable to modify their alerts or dashboards but this configuration will increase data ingest.

• Add an interface for our error API. Our error API can now be called via the code NewRelic.getAgent().getErrorApi() 1577

• Add log4j2 JsonLayout support and support log4j2 till latest. 1545

• Add httpstatus in the external segment for Spring Webclient 1610

• Enable slow transaction detection by default and bump the threshold to 10 minutes 1629

• Add support for string formatting with JBoss Logging. 1650

• Add logic to remove specific classes from being excluded from being weaved if the IAST security feature is enabled. 1453

The affected classes belong in the following formats:

• ^java/security/.*
• ^javax/crypto/.* These are crypto classes which can cause class circularity errors if they get too far along in the class transformer.
• ^net/sf/saxon.*

If you wish to re-include these excluded rules, you can do so via the following means.

YAML:

class_transformer:
    excludes: ^javax/crypto/.*,^java/security/.*,^net/sf/saxon.*

System property:

-Dnewrelic.config.class_transformer.excludes=^javax/crypto/.*,^java/security/.*,^net/sf/saxon.*

Environment variable:

NEW_RELIC_CLASS_TRANSFORMER_EXCLUDES=^javax/crypto/.*,^java/security/.*,^net/sf/saxon.*

• Prevent license_key value from being written to the agent logs when using debug and/or audit_mode logging 1653

IAST

• The IAST feature now also supports Async HTTP client version 2 and above 142
• Added support for Sun Net HTTP Server 142
• JSON version bump to 1.1.1 142
• Add critical error logging via LogMessage event 142

Fixes

• Fix transaction naming in Spring controllers with a CGLIB proxy. Transactions now use the actual class name as opposed to the proxied class name. 1574
• Fix a NullPointerException caused by ServletContext in servlet instrumentation modules. 1636
• Fix a memory leak caused by Lettuce instrumentation. Duplicate code for transaction linking has been removed from the Lettuce instrumentation and is handled by netty-reactor instead. 1608
• Fix a bug where invalidating a license key causes a memory leak. Reconnection tasks are now capped in the event of a LicenseException. 1606
• Fix a NullPointerException caused by RPMServiceManager 1604
• Add a workaround for a memory leak that may occur in rare scenarios with instrumentation using the legacy async API in the Java Agent (which async servlets and Jetty Continuations use). 1555

You can configure the option via the following means:

Agent config file (this will update dynamically if the config file is changed)

common: &default_settings
  legacy_async_api_skip_suspend: true

System Property

-Dnewrelic.config.legacy_async_api_skip_suspend=true

Environment Variable

NEW_RELIC_LEGACY_ASYNC_API_SKIP_SUSPEND=true

IAST

• DynamoDB v2 issue: missing attribute values for conditionCheck method in case of transactWriteItems operation on DynamoDB 142

• Fixed an Insecure cookie attack vulnerability. 142

• Never print LicenseKey 142

Deprecations

The following instrumentation modules are deprecated and will be removed in the next major release:

• aws-wrap-0.7.0
• java.completable-future-jdk8
• play-2.3
• spring-3.0.0
• netty-3.4
• Struts v1

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.10.0 and 7.11.0, the results printed to the console will display:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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

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.

New features and improvements

• Adds support for Java 21 1546

• Add experimental config option to run the agent with unsupported java versions 1480

• Add intrinsic attribute thread.id to spans to allow for faceting queries by thread ID 1513

• Include stack traces in client spans 1507

• Adds support for getting the containerId from a docker container with Linux cgroup v2. 1529

• Add database and external span attributes to correlate to metric data in accordance with Open Telemetry specs. Certain old attributes are removed. 1525

  New attributes:

  • db.system
  • db.operation
  • db.collection
  • server.address
  • server.port

  Removed attributes:

  • component
  • peer.hostname

• Add slow transaction detection which can be configured. It is disabled by default. 1542 E.g:

  slow_transactions:
    enabled: true
    threshold: 1000 # The threshold is measured in milliseconds

  카피

• Add instrumentation for r2dbc postgresql 0.9.2 to 0.9.x 1410

• Security Agent: Add new configuration to enable/disable low priority instrumentation security.low-priority-instrumentation.enabled for the CSEC agent. Default value is false. 1515

• Security Agent: Cassandra DB v3.0+ Support: The Security agent now supports Cassandra DB version 3.0 and above 122

• Security Agent: HttpClient v5.0+ Support: The Security agent now also supports HttpClient version 5.0 and above 122

• Security Agent: Support for std-out logging 122

• Security Agent: Added feature for Daily log rollover 122

• Security Agent: Support for logger config: log_file_count and log_limit_in_kbytes 122

• Security Agent: Relocating all our instrumentation packages under the package com.newrelic.agent.security.instrumentation.* 122

Fixes

• Fixed a bug where a ClassCircularityError was thrown by Sonarqube9.9 1522

• Fix a bug where the Java agent fails to detect spring-security-oauth2-client.jar 1462

• Fix a bug where Spring 6/ Spring Boot3 does not report underlying exception/stacktrace when a @RestControllerAdvice class is used 1538

• Fix HttpUrlConnection instrumentation so segment timing is accurate 1537

• Fixes a bug in Spring 6 instrumentation where transactions are incorrectly named in certain scenarios. 1544 Such include:

  • "built-in" controllers that don't have @RestController-like annotations, e.g. /actuator/health (see Actuator endpoints)
  • custom controllers that don't use @RestController directly (e.g. using custom annotations)
  • requests returning 401s / 404s

• Add a fix for JBoss EAP / Wildfly where if customers are using the J2EE/Jakarta Management API, the application fails to startup. 1549 This is done by adding the system property com.newrelic.jboss.jsr77.fix and setting it to true. E.g.

  -Dcom.newrelic.jboss.jsr77.fix=true

  카피

  Customers using JBoss EAP 7.4+ or Wildfly 23+ will need to manually configure the io.undertow.servlet module and add java.management as a dependency. This translates to doing the following steps:

  1. Opening the file modules/system/layers/base/io/undertow/servlet/main/module.xml
  2. Adding the XML element <module name="java.management"/> inside the body of the <dependencies> tag

  Here is what the configured XML file may look like:

  <module name="io.undertow.servlet" xmlns="urn:jboss:module:1.9">
      <resources>
          <resource-root path="undertow-servlet-2.2.5.Final-redhat-00001.jar"/>
      </resources>
  
      <dependencies>
          <module name="javax.annotation.api"/>
          <module name="sun.jdk"/>
          <module name="javax.servlet.api"/>
          <module name="javax.servlet.jsp.api"/>
          <module name="javax.servlet.jstl.api"/>
          <module name="org.jboss.logging"/>
          <module name="io.undertow.core"/>
          <module name="org.jboss.xnio"/>
          <module name="jdk.unsupported"/>
          <module name="java.management"/>
      </dependencies>
  </module>

  카피

• Resolve missing class exception on Scala instrumentation 1528

• Security Agent: Fixed ClassNotFoundException for IOStreamHelper class with Glassfish 122

Security

• Update agent dependency commons-codec to v1.13 1548
• Update JFR daemon to 1.11.1. This upgrade updates the underlying OkHttp dependency to version 4.12.0 1561

Deprecations

The following instrumentation modules will be removed in the next major release:

• aws-wrap-0.7.0
• java.completable-future-jdk8
• play-2.3
• spring-3.0.0
• netty-3.4
• Struts v1

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.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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

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.

New features and improvements

• Support latest Wildfly #1373

• Support latest JBoss EAP #1336

• Spring Cache instrumentation #1458

This new instrumentation module allows you to see how your caches are performing. It provides hit/miss metrics as well as clear and evict. Search "Metrics Explorer" for the new metrics:

Cache/Spring/<cache-provider>/<cache-name>/hits
Cache/Spring/<cache-provider>/<cache-name>/misses
Cache/Spring/<cache-provider>/<cache-name>/clear
Cache/Spring/<cache-provider>/<cache-name>/evict

• Kafka client node metrics #1338

This is a new instrumentation for Kafka clients. It provides metrics similar to the existing instrumentation module, but this provides them by node/topic, whereas the existing one only uses topic. This module is disabled by default, check the documentation for more information.

• Kafka client config events #1338

This new instrumentation module sends the Kafka configuration as events periodically. This module is disabled by default, check the documentation for more information.

• Improved Struts 2 instrumentation #1457

The Struts 2 instrumentation has been refactored to use a newer instrumentation technique, which allows it to be disabled.

• Improved code-level metrics for Servlets. #1394
• Security Agent: Support for Apache log4j 3.0.0-alpha1.
• Security Agent: Support for Commons.jxpath.
• Security Agent: Add agent monitoring details and matrix to health check.
• Security Agent: Limiting the supported version range for Jetty.

Fixes

• Fixed a bug in the Spring instrumentation when OpenFeign was used. #1197
• Fixed a bug where utility classes were not weaved. #1073
• Fixed a bug where the agent would not properly send its dependencies. #1340
• Security Agent: Issue with HealthChecking having empty process stats issue

Deprecations

• aws-wrap-0.7.0
• java.completable-future-jdk8
• play-2.3
• spring-3.0.0
• netty-3.4
• Struts v1 (legacy pointcut instrumentation)

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.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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

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.

Note: This release note has been corrected to remove Struts 2 from the list of deprecations.

New features and improvements

• Kafka Connect instrumentation: Adds metrics and transaction tracing for version 2.0.0+ #1324
• Kafka: Added metrics to understand the relationship between consumers, producers, topics and nodes #1223
• IAST: Limiting the supported version range for Apache log4j due to the new version release of Apache log4j on 21 June 2023 #80
• IAST: Support for indication what all API-IDs are scanned or being scanned #80
• All existing instrumnetation now supports Jakarta 10 EE

Fixes

• Implement the getStatus() method in the NRWrapper class for version 5 and 6 of Servlet instrumentation #1315

Deprecations

• aws-wrap-0.7.0
• java.completable-future-jdk8
• play-2.3
• spring-3.0.0
• netty-3.4
• Struts 1 (legacy pointcut instrumentation)

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.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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

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.

New features and improvements

• Added a public preview of the Interactive Application Security Testing (IAST) mode of the New Relic Security agent.

To learn about how to use IAST, check out our documentation.

By default, the New Relic Security agent IAST mode is completely disabled. To enable it, set both newrelic.config.security.agent.enabled=true and newrelic.config.security.enabled=true.

Full configuration options are detailed below (note that the security section should be indented two spaces under the pre-existing common section in the newrelic.yml config file):

# New Relic Security vulnerability detection.
  security:
    # Determines whether the security data is sent to New Relic or not. When this is disabled and agent.enabled is
    # true, the security module will run but data will not be sent. Default is false.
    enabled: false

    # New Relic Security provides two modes: IAST and RASP
    # Default is IAST. Due to the invasive nature of IAST scanning, DO NOT enable this mode in either a
    # production environment or an environment where production data is processed.
    mode: IAST

    # New Relic Security's SaaS connection URL
    validator_service_url: wss://csec.nr-data.net

    # To completely disable all security functionality, set this flag to false. This property is
    # read only once at application start. Default is false.
    agent:
      enabled: false

    # These are the category of security events that can be detected. Set to false to disable detection of
    # individual event types. Default is true for each event type.
    detection:
      rci:
        enabled: true
      rxss:
        enabled: true
      deserialization:
        enabled: true

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.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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

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.

New features and improvements

• Batch payloads and compression for Infinite Tracing: Enhanced performance by providing option to enable payload compression and batching for Infinite Tracing 1146.

• HttpClient v5.0+ support: The Java agent now supports HttpClient version 5.0 and above 1252.

• On-the-fly class retransformation: Classes with Trace annotation are now retransformed upon attach, enhancing instrumentation flexibility 1147.

• Enhanced logging for Cats Effect 2: Log Cats Effect 2 instrumentation at finest log level 1173.

• High-security mode disables user tracking 1261.

• Selective RollingFileAppender Usage: The RollingFileAppender is now only used when log_limit_in_kbytes is greater than 0, improving logging efficiency 1228.

Fixes

• Fixed Cats Effect 2 logging: Addressed issues with Cats Effect 2 logging for better reliability 1269.

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.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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

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.

New features and improvements

• Added support for Java 20 1226

Fixes

• Prevented a NullPointerException from the lettuce instrumentation 1204
• Fix failure with browser agent auto injection for tomcat versions 8.5.87+ and 9.0.74+ 1225

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.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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

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.

새로운 기능 및 개선 사항

• Webflux 6 1181지원이 추가되었습니다.

• Spring JMS 6 1088지원이 추가되었습니다.

• MongoDB 반응형 스트림 지원이 추가되었습니다(버전 1164).

• Kafka Streams 1170지원이 추가되었습니다.

  Kafka Streams 지원은 메트릭과 스팬이라는 두 가지 방식으로 제공됩니다. 메트릭은 기본적으로 활성화되어 있고, 스팬은 기본적으로 비활성화되어 있습니다. 스팬을 활성화하려면 newrelic.yml 파일의 common 섹션 아래 설정에 다음 내용을 추가하세요.

common:
  class_transformer:
    kafka-streams-spans:
      enabled: true

• 오류 지문 - 자체 오류 수신함(errors inbox) 그룹 이름을 제공하세요 1195

  에러 발생이 잘못 그룹화되어 있습니까? 콜백 함수를 통해 자체 에러 핑거프린트를 설정하십시오. 사용자 정의 proc를 허용하는 새로운 공개 API 메서드가 추가되었습니다. proc는 감지된 각 에러에 대해 호출되며, 문자열을 반환할 때마다 해당 문자열이 에러의 에러 그룹 이름으로 사용되고 뉴렐릭 에러스 인박스(errors inbox)에서 발생하는 모든 서버 측 그룹화보다 우선 적용됩니다. 이를 통해 사용자는 에러 그룹화에 대해 훨씬 더 많은 제어 권한을 가질 수 있습니다. 자세한 내용은 API: 에러 그룹화 및 APM: 에러 그룹 탭 페이지를 확인하십시오.

• 사용자 추적 - 오류를 사용자 ID 1188과 연결

  이제 오류 그룹의 영향을 받는 사용자 수를 확인할 수 있습니다. 사용자 ID의 문자열 표현을 허용하고 해당 사용자 ID를 현재 트랜잭션과 연결하는 새로운 공개 API 메서드로 최종 사용자를 식별하십시오. 그러면 트랜잭션과 오류에 새로운 enduser.id 에이전트 속성이 연결됩니다. 이를 통해 에이전트 사용자는 더 나은 필터링 및 알림 기능을 지원하기 위해 트랜잭션과 오류를 특정 사용자 ID에 속하는 것으로 태그할 수 있습니다. 자세한 내용은 [Newrelic.setUserId ](https://newrelic.github.io/java-agent-api/javadoc/com/newrelic/api/agent/NewRelic.html#setUserName(java.lang.String) 문서 및 에러스 인박스(errors inbox)로 영향을 받는 사용자 추적 페이지를 확인하십시오.

• 소니 외부에서 token.link() 호출하면 해당 메소드가 비동기 프로세서 1140을시작하게 됩니다.

• Kafka 클라이언트 측정, 로그에는 노드를 나열하는 새로운 지표가 있습니다: MessageBroker/Kafka/Nodes/<node> 1130

수정 사항

• 에이전트가 1137을연결할 때 발생하는 ClassCircularityError를 수정합니다.
• addCustomAttributes 1115호출 시 발생하는 NullPointerException 오류를 수정합니다.
• TokenAndRefCount.token 이 절대 null이 되지 않도록 하세요 1149
• 복제가 포함된 MySQL 클라이언트에서 메모리 누출을 방지하기 위해 시간 기반 캐시를 사용하여 데이터베이스 연결 데이터 저장 1114
• HttpUrlConnection 측정에서 사용되는 스레드 수를 줄였습니다. (계측 1145)
• HttpUrlConnection을 실내외 인테리어 tracing 1142와 함께 사용할 때 발생하는 문제 수정
• Netty의 RequestWrapper 1163 버전에서 성능이 향상되었습니다.
• 시작 시 문제가 발생하면 에이전트를 정상적으로 종료합니다 . 1136
• 생성자에 WeavedMethod 및 InstrumentedMethod 어노테이션을 적용할 때 발생하는 문제를 수정했습니다. 1153
• Tomcat 1131사용 시 성능 향상
• 에이전트가 일부 예외를 보고하지 않는 버그를 수정했습니다 (버전 1176).
• DockerData를 업데이트하여 감지된 컨테이너 ID 수를 1178개로 늘렸습니다.
• Kafka 클라이언트에서 사용되는 스레드 수를 줄이세요. 측정, 계측 1056
• 문법 변경 사항 [1175](https://github.com/newrelic/newrelic-java-agent/pull/1175) 및 [1190]https://github.com/newrelic/newrelic-java-agent/pull/1190)

최신 버전으로 업데이트

현재 사용 중인 Java 에이전트 버전을 식별하려면 java -jar newrelic.jar -v 을 실행합니다. Java 에이전트 버전이 콘솔에 인쇄됩니다.

그런 다음 최신 Java 에이전트 버전으로 업데이트하려면 다음을 수행합니다.

1. 전체 Java 에이전트 루트 디렉터리 를 다른 위치에 백업합니다. 해당 디렉토리의 이름을 NewRelic_Agent#.#.# 으로 바꿉니다. 여기서 #.#.# 은 에이전트 버전 번호입니다.
2. 에이전트를 다운로드합니다.
3. 새 에이전트 다운로드 파일의 압축을 푼 다음 newrelic-api.jar 및 newrelic.jar 을 원래 Java 에이전트 루트 디렉토리 에 복사합니다.
4. 이전 newrelic.yml 을 zip에서 새로 다운로드한 newrelic.yml 과 비교 하고 필요한 경우 파일을 업데이트합니다 .
5. Java 디스패처를 다시 시작하십시오.

Java 에이전트 업데이트 후 문제가 발생하면 백업된 New Relic 에이전트 디렉터리에서 복원하십시오.

에이전트 구성 차이점 업데이트

에이전트의 새 버전을 출시할 때 newrelic.yml 에 새 설정을 추가합니다.diff 또는 다른 diffing 유틸리티를 사용하여 변경된 사항을 확인하고 이전 파일에 새 구성 설정을 추가할 수 있습니다.라이센스 키, 앱 이름 또는 기본 설정 변경 사항과 같이 파일에 대해 수행한 사용자 정의를 덮어쓰지 않도록 하십시오.

예를 들어, יאני 버전 7.10.0 및 7.11.0에 대한 기본 newrelic.yml 파일을 diff 하는 경우 콘솔에 인쇄된 결과는 다음과 같습니다.

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

이 예에서 이러한 줄은 Java의 기본값 newrelic.yml 에 추가되었습니다. 7.11.0 이상 버전으로 업그레이드하는 경우 원래 newrelic.yml 에 다음 새 줄을 추가해야 합니다.

지지 성명:

• 뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 또한, 이전 버전은 지원이 종료 되면 더 이상 지원되지 않습니다.