Skip to content

Latest commit

 

History

History
1330 lines (971 loc) · 86.3 KB

CHANGELOG.md

File metadata and controls

1330 lines (971 loc) · 86.3 KB
Raw

Changelog

Noteworthy changes to the agent are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Version 8.14.0

New features and improvements

  • The Java agent supports disabling AI Monitoring at the account/organization level 1972
  • HikariCP instrumentation now captures additional metrics 1976
  • Adds new instrumentation module for kafka-clients-metrics-3.7.0 2001
  • Adds new instrumentation module for jedis-5.0.0 1969
  • Adds new instrumentation module for vertx-sqlclient-4.4.2 2004
  • The newrelic-scala-api for Scala 3 will now be published to Maven 1995
  • New AWS MQ attributes will be added to spans 1977
  • Clarify Javadoc comments for @Trace API 2009

Fixes

  • Fixes a netty-reactor issue that was causing high memory usage 1978
  • Netty instrumentation will start transactions for HTTP/2 requests 1994

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

IAST

Version 8.13.0

New features and improvements

  • Add attributes to AWS SQS spans that allow linking to SQS entities 1954
  • Add support for Graphql 22.0+ 1912
  • Add support for JSP v4 1951
  • Add instrumentation for HikariCP 2.4.0 to replace existing extension module.1964
    • Note: If the New Relic HikariCP incubator module is currently in use, delete it from the new relic jar’s extension folder before upgrading to this version of the Java Agent.
  • Enhance CompletableFuture instrumentation for JDK11+ 1908
  • Enable RUM script injection via JSP v3 Tag library 1943
  • Fetch the docker container ID for ECS Fargate instances 1952

Fixes

  • Fix R2dbc postgresql 0.9.2 instrumentation to prevent memory leaks 1916
  • Update vertx-web instrumentation to start transactions for HTTP/2 requests 1959
  • Update JFR Instance Naming to display correct number of JVMs 1928
  • Close instrumentation gap for akka-http 10.2.0+ 1955
  • Start transactions in the Jetty12 core server 1950
  • Clean up dtTracers and externalTracers after exceptions to prevent memory leaks 1902
  • Add security-related class excludes during normal class transformer creation 1918
  • Add null checks to vertx 4.5.1 instrumentation 1927

IAST

Deprecations

  • The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

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

Version 8.12.0

New features and improvements

  • Add support for Java 22 1819
  • Add AI Monitoring support for AWS SDK for Java v2 Bedrock Runtime Client versions 2.20.157 and above 1837
  • Enhance log forwarding to include "caused by" section 1857
  • Add support for Pekko Http #1850
  • Add local decorating for Log4j 2 users utilizing JsonTemplateLayout 1866
  • Performance improvements on SQL checks 1887

Fixes

  • Resolve various thread hopping issues with Spring Reactor call chains 1883
  • Refactor the daily logfile rolling job to support all platforms 1888
  • Fix Ning memory leak 1903

IAST

Update Security Agent to Public Release version 1.3.0 1896

Deprecations

  • The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

  • 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

Version 8.11.1

New features and improvements

  • Update Security Agent to Public Release version 1.2.1

Deprecations

  • The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

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

IAST

Version 8.11.0

New features and improvements

  • Add HTTP/2 support for Netty 4.1.16.Final + 1815

  • Support external calls inside Spring Reactor call chains 1828

  • Support for Apache Pekko (i.e. the pekko-actor library). Support for Pekko HTTP coming soon. 1811

  • Add configuration to allow the OTel SDK integration to be completely disabled 1821

    Configuration via yaml:

    opentelemetry:
  sdk: 
    autoconfigure:
      enabled: false

    Configuration via system property:

      -Dnewrelic.config.opentelemetry.sdk.autoconfigure.enabled=false

  • Treat OpenTelemetry @WithSpan annotation as @Trace in the Java Agent API 1841

Fixes

  • Fix high CPU usage with HttpURLConnection by reverting InboundWrapper changes introduced in 8.10.0 1840
  • Prevent duplicate HTTP external calls when using the DynamoDB SDK 1827

Deprecations

  • The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

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

IAST

Changes

  • Json Version bump to 1.2.0 207
  • IAST replay header decryption due to Security Findings 207

Fixes

  • Fix issue related to the instrumentation of the Rhino JavaScript Engine that occurred while reading the script 211

Version 8.10.0

⚠️ CAUTION: This agent version introduced a bug that may cause significant increases in CPU and memory usage and potential deadlock if your application uses HttpUrlConnection (or any libraries that use it under the hood). This issue has been resolved in the 8.11.0 agent. Alternatively, disabling the HttpUrlConnection instrumentation would prevent the issue (for example -Dnewrelic.config.class_transformer.com.newrelic.instrumentation.httpurlconnection.enabled=false).

PLEASE NOTE: Disabling this instrumentation will result in external calls made by the client no longer getting recorded. We strongly recommend using the latest agent versions, which include all recent code fixes and provide access to the latest platform features.

New features and improvements

  • Support for Spring Webflux 6.1.x 1761

  • Support for Spring Batch v4.0+ 1792

  • Scala 3 API 1772

  • ZIO 1 instrumentation improvements 1739

  • Support for ZIO 2 1778

    For more information see Scala ZIO instrumentation

  • Enhanced clustered Solr JMX metrics 1812

  • Add transaction GUID to Errors 1813

Fixes

  • Prevent NullPointerException when setting the user id outside of a transaction 1762
  • Disallow Real Time Profiling when High Security Mode is enabled 1764
  • Prevent ClassCircularityErrors in some specific circumstances 1763
  • Properly removing files when log_daily is enabled 1754
  • Decreased memory held by the agent when HTTP calls are made 1775
  • Prevent duplicate DT headers for gRPC 1783
  • Properly updating how many log messages are sent after configuration change 1784
  • Prevent exceptions when reading lambda bytecode 1794
  • Reduce interval for JDBC caches 1809

Deprecations

-The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

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

IAST

Changes

  • Ning Async HTTP client Support: The security agent now also supports com.ning:async-http-client 1.0.0 and above 152, 118, 116
  • Jersey Support: The security agent now also supports Jersey 2.0 and above 150, 149
  • Mule Support: The security agent now also supports Mule server version 3.6 to 3.9.x 144, 143
  • Jetty v12 Support: The security agent now also support Jetty version 12 and above 106
  • Lettuce Support: The security agent now also supports Lettuce 4.4.0.Final and above 125

Fixes

  • Extract Server Configuration to resolve IAST localhost connection with application for Wildfly server 192
  • Trustboundary events now will have list of string as parameter schema

Version 8.9.1

Fixes

  • Check HttpHost instance for null prior to dereferencing it when certain execute() methods are called 1722
  • Do an instanceof check in the complete() method prior to class cast 1719
  • Null check on the response object prior to trying to report an external call 1719

Deprecations

  • The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

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

Version 8.9.0

New features and improvements

  • Instrumentation for Spring Webclient 5/6 now captures http status code and http status message 1658
  • Add status code to grpc-1.40.0 client instrumentation 1673
  • Add config to set the size limit of attributes on custom events (i.e. newrelic.config.custom_insights_events.max_attribute_value). Default size is 255 characters and the max is 4095. 1683
  • Add Spring instrumentation modules to support proper transaction naming (route + HTTP method) of traditional annotated spring controllers as well as controllers that inherit annotations from interfaces, super classes or custom annotations. Note that because the new instrumentation can change transaction names, enabling this "enhanced transaction naming" is gated by the newrelic.config.class_transformer.enhanced_spring_transaction_naming agent configuration option, which is false by default. Thanks to @mgr32 for their help with validating the naming changes. 1675
  • Add instrumentation for Vert.x 4.5.x web client and futures 1704

Fixes

  • Remove erroneous printing of stack trace in SlowTransactionManager 1684
  • Convert the ProcessPointCut over to a weaver instrumentation module to better handle cases where it is used in a multi-threaded environment. 1685

Removals

  • Remove support for setting agent config with rarely used lower-case, dotted environment variable names (e.g. newrelic.config.labels). Customers relying on lower-case, dotted environment variables should switch to the standard upper-case, underscore names (e.g. NEW_RELIC_CONFIG_LABELS). There are no changes to documented system property behavior (via newrelic.config., server-side config, YAML, or standard environment variable (via NEW_RELIC_). 1598

Deprecations

  • The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

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

IAST

Version 8.8.1

Fixes

  • Fixed a NullPointerException when working with Synthetics headers 1690

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

Version 8.8.0

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

    The option can be configured 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

Full Changelog: https://github.com/newrelic/newrelic-java-agent/compare/v8.7.0...v8.8.0

Version 8.7.0

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

Version 8.6.0

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 its documentation for more information.

  • Kafka client config events #1338

This new instrumentation module sends the Kafka configuration as events periodically.

  • 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

Version 8.5.0

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 v1 and v2 (legacy pointcut instrumentation)

Full Changelog: https://github.com/newrelic/newrelic-java-agent/compare/v8.4.0...v8.5.0

Version 8.4.0

New features and improvements

Version 8.3.0

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

Full Changelog: https://github.com/newrelic/newrelic-java-agent/compare/v8.2.0...v8.3.0

Version 8.2.0

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

Full Changelog: https://github.com/newrelic/newrelic-java-agent/compare/v8.1.0...v8.2.0

Version 8.1.0

New features and improvements

  • Added support for Webflux 6 1181

  • Added support for Spring JMS 6 1088

  • Added support for Mongodb Reactive Streams 1164

  • Added support for Kafka Streams 1170

    Support for Kafka Streams comes in two flavors, metrics and spans. Metrics are enabled by default, while spans are disabled by default. To enable spans add the following to your newrelic.yml configuration under the common stanza:

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

  • Error fingerprint - supply your own errors inbox group names 1195

    Are your error occurrences grouped poorly? Set your own error fingerprint via a callback function. A new public API method has been added that will accept a user defined proc. The proc will be invoked for each noticed error and whenever it returns a string, that string will be used as the error group name for the error and will take precedence over any server-side grouping that takes place with the New Relic errors inbox. This gives users much greater control over the grouping of their errors. For more information check our API: Error Grouping and APM: Group errors tab pages.

  • User tracking 1188

    You can now see the number of users impacted by an error group. Identify the end user with a new public API method that will accept a string representation of a user id and associate that user id with the current transaction. Transactions and errors will then have a new enduser.id agent attribute associated with them. This will allow agent users to tag transactions and errors as belonging to given user ids in support of greater filtering and alerting capabilities. For more information check the [Newrelic.setUserId ](https://newrelic.github.io/java-agent-api/javadoc/com/newrelic/api/agent/NewRelic.html#setUserName(java.lang.String) documentation and the Track users impacted with errors inbox page.

  • Invoking token.link() outside a transaction will instrument that method to start an async transaction 1140

  • The Kafka clients instrumentation has new metrics to list the nodes: MessageBroker/Kafka/Nodes/&lt;node> 1130

Fixes

  • Fix ClassCircularityError when agent attaches 1137
  • Fix NullPointerException thrown when calling addCustomAttributes 1115
  • Make sure TokenAndRefCount.token is never null 1149
  • Using a time based cache to store database connection data to prevent a memory leak when instrumenting MySQL client with replication 1114
  • Decreased the number of threads used in the HttpUrlConnection instrumentation 1145
  • Fix an issue when HttpUrlConnection is used with the legacy cross application tracing 1142
  • Performance improvement in Netty’s RequestWrapper 1163
  • Gracefully shutdown the agent if it encounters issues on startup 1136
  • Fix WeavedMethod and InstrumentedMethod annotations when applied to constructors. 1153
  • Performance improvements when using Tomcat 1131
  • Fixed a bug that caused the agent to not report some exceptions 1176
  • Updated DockerData to increase the number of container IDs detected 1178
  • Reduce the number of threads used in Kafka clients instrumentation 1056
  • Grammar changes 1175 and 1190

Full Changelog: https://github.com/newrelic/newrelic-java-agent/compare/v8.0.1...v8.1.0

Version 8.0.1 (2023-02-23)

Fixes

  • Various fixes to the HttpUrlConnection instrumentation. See the README for full details #1145
  • Ensure that TokenAndRefCount.token is never null #1148
  • Correct a possible NullPointerException being thrown when calling addCustomAttributes #1141
  • Fix ClassCircularityError when agent attaches #1139

Full Changelog: https://github.com/newrelic/newrelic-java-agent/compare/v8.0.0...v8.0.1

Version 8.0.0 (2023-01-26)

Important

This release includes a change to the HttpURLConnection instrumentation that creates a TimerTask to help ensure complete externals reporting. Under some circumstances this may result in a large number of threads being created, which may exhaust the maximum allocated to the JVM, causing it to stop. This issue has been fixed in the 8.0.1 release and it is highly recommended that you update to this version of the Java agent.

New features and improvements

  • Added support for Slick 3.4.0 on Scala 2.13 #1072
  • Added support for Embedded Tomcat JMX #1039
  • Updated the Java agent’s snakeyaml dependency to 1.33 #1077
  • Added tracer debug logging, which will appear when -Dnewrelic.config.log_level=finest and -Dnewrelic.debug=true are set #1066
  • Improved logging when using the recordCustomEvent API now includes event type, key and value #1083
  • Added Log4j1 instrumentation to support auto log forwarding #1097
  • Added JBoss Logging instrumentation to support auto log forwarding #1126
  • Real-time profiling for Java using JFR metrics can now be dynamically enabled/disabled via agent configuration #1124

Fixes

  • Removed leading slash in JCache metric names #1112
  • Fixed a bug that was preventing Log4j2 metrics from getting disabled properly #1068
  • Added a missing delimiter in POSTGRES_DIALECT_PATTERN #1050
  • Fixed a ClassCastException in GraphQL 16/17 #1082
  • Refactored HttpURLConnection instrumentation to fix several bugs that were affecting external calls and distributed traces #1102
  • Refactored grpc-1.40.0 instrumentation to ensure that tokens were properly being linked across threads #1105
  • Fixed a bug that was causing transactions to fail to link when the Spring Webclient would timeout and emit a ReadTimeoutException #1109

Removals

The following previously deprecated instrumentation modules were removed:

  • cassandra-datastax-2.1.2
  • httpclient-3.0
  • jdbc-embedded-derby-10.2.1.6
  • jdbc-embedded-derby-10.10.1.1
  • jetty-7
  • jetty-7.6
  • jetty-9
  • jetty-9.0.4
  • jetty-9.1
  • mongodb-2.12
  • mongodb-2.14
  • mongodb-3.0
  • okhttp-3.0.0
  • okhttp-3.4.0
  • okhttp-3.5.0

The previously deprecated httpResponseCode, response.status and response.statusMessage transaction/span attributes were removed. These have been replaced by http.statusCode and http.statusText. If you have any custom dashboards or alerts that query the httpResponseCode, response.status, and response.statusMessage attributes then they will need to be updated to instead use http.statusCode and http.statusText.

Version 7.11.1 (2022-11-15)

New features and improvements

Fixes

  • Fix bug with log4j2 metrics #1068
  • Adds a previously missing delimiter in POSTGRES_DIALECT_PATTERN "|" #1050
  • Update snakeyaml lib to v1.33 security patch #1077

Deprecation notice

The following instrumentation modules have been deprecated for removal:

  • cassandra-datastax-2.1.2
  • httpclient-3.0
  • jdbc-embedded-derby-10.10.1.1
  • jetty-7
  • jetty-7.6
  • jetty-9
  • jetty-9.0.4
  • jetty-9.1
  • mongodb-2.12
  • mongodb-2.14
  • mongodb-3.0
  • okhttp-3.0.0
  • okhttp-3.4.0
  • okhttp-3.5.0

The httpResponseCode, response.status and response.statusMessage transaction/span attributes are deprecated and will be removed in a future release. These have been replaced by http.statusCode and http.statusText.

Full Changelog: https://github.com/newrelic/newrelic-java-agent/compare/v7.11.0...v7.11.1

Version 7.11.0 (2022-10-27)

New features and improvements

  • Support Java 19 1022
  • Support Play 2.8.16+ 981
  • Support ojdbc8 v21.1.0.0+ 1042
  • Support Semeru/OpenJ9 JVMs 993
  • Support log forwarding for java.util.logging (JUL) 1049

Support forwarding log context data 866

The agent can now forward data in Mapped Diagnostic Context (MDC, logback/slf4j) and ThreadContext (log4j2) as attributes when forwarding log records. When the feature is enabled, these attributes will be added to the log records with a context. prefix. For details on how to enable this feature see the documentation for context_data.

Custom Event Limit Increase 1036

This version increases the default limit of custom events from 10,000 events per minute to 30,000 events per minute. In the scenario that custom events were being limited, this change will allow more custom events to be sent to New Relic. There is also a new configurable maximum limit of 100,000 events per minute. To change the limits, see the documentation for max_samples_stored. To learn more about the change and how to determine if custom events are being dropped, see our Explorers Hub post.

Code-level metrics on by default 1037

The code-level metrics functionality introduced with agent 7.10 is now enabled by default. This feature will cause an increase in the consumption of data. The amount depends on the application. To disable code-level metrics, see instructions on our code-level metrics documentation.

Fixes

  • Prevent an exception from being thrown in the Jedis instrumentation 1011
  • Improvement on Http4s transactions 1006
  • Fix noticeError API not verifying whether errors were expected 1014
  • Add operation for Lettuce queries to clusters 1031
  • Fix exception when building up the agent jar from a clean repo 1048
  • Better error handling for code-level metrics 1021 1051
  • Fix HttpUrlConnection spans not terminating on exception 1053

Deprecation notice

The following instrumentation modules are being deprecated for removal:

  • cassandra-datastax-2.1.2
  • httpclient-3.0
  • jdbc-embedded-derby-10.10.1.1
  • jetty-7
  • jetty-7.6
  • jetty-9
  • jetty-9.0.4
  • jetty-9.1
  • mongodb-2.12
  • mongodb-2.14
  • mongodb-3.0
  • okhttp-3.0.0
  • okhttp-3.4.0
  • okhttp-3.5.0

The httpResponseCode, response.status and response.statusMessage transaction/span attributes are deprecated and will be removed in a future release. These have been replaced by http.statusCode and http.statusText 513

Full Changelog: https://github.com/newrelic/newrelic-java-agent/compare/v7.10.0...v7.11.0

Version 7.10.0 (2022-09-13)

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 21.0.0.12+

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

Fixes

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

Version 7.9.0 (2022-08-28)

New features and improvements

  • Where applicable, existing instrumentation has been tested and verified as compatible with Jakarta EE 8. 900
  • Add new instrumentation to support Jetty 10. 936
  • Update to jfr-daemon 1.9.0 to address CVE-2020-29582 and improve CPU overhead. 937
  • Add support to pass a boolean environment variable NEWRELIC_DEBUG where setting it to true activates the debug configuration. 890
  • Improved performance by internally replacing regex replace with iterative char replace (thanks to @zowens for this contribution) 933

Fixes

  • Update the httpurlconnection instrumentation to use newer distributed tracing APIs so that spans are correctly marked as external calls in distributed traces and contain the expected http.* attributes. 885
  • Illegal Access Exception is no longer thrown from apps using NR agent with scala 2.12 and Java 11. 876

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.

Version 7.8.0 (2022-06-16)

New features and improvements

  • Updated the agent to use caffeine 2.9.3 832
  • Refactored the log.level attribute name on LogEvents to instead be level 858
  • Kafka instrumentation - supports metrics for kafka-clients versions 3.x. 860 and 865
  • Update to jfr-daemon 1.8.0 869
  • Lettuce instrumentation - supports lettuce-core 4.3 up to 6.x. Please remove any other (experimental/incubating) lettuce extensions or else Redis database metrics could be doubled. 872

Fixes

  • Fixed CQLParser getOperationAndTableName exception handling. Exceptions are now handled within the CQLParser. 857
  • Removed akka-http-core bindAndHandle instrumentation to resolve scenarios where duplicated transactions could result 850 (see Scala Akka HTTP core instrumentation for more details)

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.

Version 7.7.0 (2022-05-03)

New features and improvements

  • Supports Java 18 813
  • APM logs in context. Automatic application log forwarding is now enabled by default. This version of the agent will automatically send enriched application logs to New Relic. To learn more about about this feature see here, and additional configuration options are available here. To learn about how to toggle log ingestion on or off by account see here. 817
  • Added instrumentation support for the Postgres, MySQL, Oracle & MSSQL R2DBC connectors 810 816 829 828

Fixes

  • Patches a security issue related to an older version of jszip that is included in the Java agent API Javadoc jar 820

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.

Version 7.6.0 (2022-04-04)

New features and improvements

  • Added built-in agent support for Logs in Context (log4j 2.6+ and Logback 1.1+). Read more about this capability on our Logs in Context feature page 718
  • Added instrumentation support for the MariaDB & H2 R2DBC connectors 799 724
  • Updated agent support for Jedis 4.0.0+ 698
  • Updated agent support for Cassandra dataStax 4+ 690

Fixes

  • Guard against intermittent null pointer exceptions 707
  • Support CSP nonce parameter for RUM header and footer 591
  • Fixed an issue with auto app naming and distributed tracing transactions 566
  • Increased maximum TransactionError message size 581
  • The httpResponseCode, response.status and response.statusMessage transaction/span attributes are deprecated and will be removed in a future release. These have been replaced by http.statusCode and http.statusText 513:

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.

Version 7.5.0 (2022-01-12)

New features and improvements

  • Update to jfr-daemon 1.7.0 - fixes a memory leak condition by cleaning up copies of JFR recordings. Also updated to use version 0.13.1 of the telemetry-sdk 638
  • Update HTTP response code attribute names. This will add http.statusCode and http.statusText to spans and transactions 513
  • Provide support for Datastax/Cassandra WrappedStatments. 525
  • Add instrumentation for gRPC 1.40.0+ (thanks to fcaylus for this contribution) 518
  • Add suppressed exceptions to ThrowableError.stackTrace (thanks to dkarlinsky for this contribution) 405
  • Add Scala instrumentation and Scala API for Monix Tasks 543
  • Add instrumentation for Mongo async/reactivestreams drivers versions 3.4.x to 4.1.x 609
  • Scala Cats Effect 3 - modified the API to support passing the transaction by implicit reference, rather than using ThreadLocal variables 578
  • Add Instrumentation for Play WS 2.6.0 under Scala 2.13 594
  • Agent optimization: change String.replaceAll in favor of Pattern.compile (thanks to brunolellis for this contribution) 592

Fixes

  • Upgrade log4j-core version to 2.17.1 to address security vulnerability CVE-2021-44832 625
  • Enhancements for Spring WebFlux and Reactor Netty instrumentation to address gaps in instrumentation. Also includes support for upgraded Spring Security configurations 538
  • Update Async-Http-Client library version to 2.0.35 to address security vulnerability CVE-2017-14063 577
  • Handle null pointer exceptions in hostname lookup 587
  • Properly expire tokens used in CompletableFuture instrumentation to reduce memory usage and prevent telemetry reporting delays 634
  • Add additional exception handling to catch ConnectionPoolTimeoutException errors, which may lead to an unrecoverable agent state 637
  • Resolve Solr FilterCache Memory Leak 613
  • Reintroduce MongoDB sync instrumentation (erroneously removed in a prior release while async support was added) 635
  • Fix Sql obfuscation so that it applies correctly to queries with certain formatting 632
  • Agent configuration expected_status_codes is not honored when a transaction exception is encountered 565
  • Scala Cats Effect - ensure Http4s transaction tracer is created on request run. This resolves some invalid tracer states that were causing null pointer exceptions 530
  • Fix Akka HTTP bindFlow 555
  • Address Caffeine cache causing memory leak and OOM condition 593

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.

Version 7.4.0 (2021-10-28)

New features and improvements

  • Support for Java 17 #433

  • Distributed Tracing is on by Default and deprecates Cross Application Tracing #486

    • Increases the default maximum number of samples stored for Span Events from 1000 to 2000.
    • The maximum number of samples stored for Span Events can be configured via the max_samples_stored configuration in the newrelic.yml.
    span_events:
  max_samples_stored: 2000

    Notice: This feature will cause an increase in the consumption of data. The amount depends on the application. This feature can be disabled by adding the following to the agent yaml config nested under the common stanza:

    distributed_tracing:
  enabled: false

  • Auto-instrumentation Support for GraphQL-Java 17.0+ #487

  • This version tested agent support for the ARM64/Graviton2 platform

Fixes

The existing MongoDB sync client instrumentation was incorrectly applying when MongoDB reactive or async client was being used, which could lead to segment timeouts and long transaction response times. #476

Deprecations/Removed Features

Cross Application Tracing is now deprecated, and disabled by default. To continue using it, enable it with cross_application_tracer.enabled = true and distributed_tracing.enabled = false.

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.

Version 7.3.0 (2021-9-30)

New features and improvements

  • Support for Java 16

  • Auto-instrumentation support for java.net.http.HttpClient

  • Migrate the Agent’s caching library from Guava to Caffeine

    • Caffeine provides an in-memory cache using a Google Guava inspired API. The improvements draw on the author’s experience designing Guava's cache and ConcurrentLinkedHashMap.
    • We expect this change to provide improvement in cases where we saw thread contention and deadlocks attributable to the Guava library.

Fixes

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.

Version 7.2.0 (2021-9-9)

New features and improvements

  • Scala Library Instrumentation #362 and #363

    • STTP versions 2 & 3 Akka-HTTP, HTTP4s and STTP core backends
    • Cats-effect v2
    • ZIO v1
    • HTTP4s client & server v0.21
    • Play 2.3-2.8
    • Akka-HTTP v10.1 & v10.2
    • For more information, see Scala instrumentation.

  • Scala API support (see PRs above)

    • Scala APIs provided for explicit instrumentation of several of above libraries in case auto-instrumentation is not desired
    • Cats-effect v2
    • ZIO v1

  • AWS v2 DynamoDB Instrumentation #343

  • GraphQL 16 Instrumentation #396

    • Create meaningful transaction names
    • Create meaningful spans
    • Reporting GraphQL errors
    • For more information, see GraphQL for Java

  • JFR feature causing excessive overhead when enabled JFR #203

    • Refactored code to use less memory.

Fixes

The existing MongoDB instrumentation was partially applying when MongoDB Reactive Streams is being used.

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.

Version 7.1.1 (2021-7-15)

Due to overhead caused in some applications Real-time profiling for Java using JFR metrics is now disabled by default.

It can be enabled following the instructions here.

Version 7.1.0 (2021-7-7)

Known issue

Some customers saw increased overhead when Real-time profiling is enabled. See instructions to disable Real-time profiling in the notice below.

New features and improvements:

  • Java instrumentation by XML new properties #288

    • traceLambda - to trace lambdas inside a method
    • traceByReturnType - to trace all methods in a class that return a given type

    These are compatible with Java and Scala. For more information, see Java instrumentation by XML.

  • Scala APIs #254

    New artifacts allow Scala code to be instrumented using a fluent Scala API instead of the Java annotations. There are specific artifacts for versions 2.10, 2.11, 2.12, 2.13 of Scala. Scala 3.0 users can use the 2.13 artifact.

    For more information, see Scala instrumentation.

  • Real-time profiling for Java using JFR metrics #333

    Real-time profiling for Java using JFR metrics is now enabled by default.

    Notice: this feature will cause an increase in the consumption of data. The amount depends on the application. It can be disabled by adding the following to the agent yaml config nested under the common stanza:

      jfr:
    enabled: false

    For more information, see JFR core README.

Version 7.0.1 (2021-6-15)

Fixes

  • Fixes an issue where the agent would break OkHttp versions 3.X and lower. #324

Version 7.0.0 (2021-6-9)

New features and improvements:

  • Real-time profiling for Java using JFR metrics
    Real-time profiling for Java using JFR metrics is now fully integrated into the Java agent. See the JFR core README for additional details.

    This feature requires a supported version of Java (Java 8 (specifically version 8u262+) or Java 11+) and is currently disabled by default. To enable it set the following in your yaml (indented 2 spaces under the common stanza).

      jfr:
    enabled: true

    Notice: If you were previously using the jfr-daemon jar as an agent extension or standalone process you should remove that option to avoid potential conflicts with the JFR service that is now built into the agent.

  • Not compatible with Java 7
    In order to continue to innovate and efficiently provide new capabilities to our customers who run on the JVM, this and future agent versions are not compatible with Java 7. If you are running Java 7, you may continue to use Java agent 6.5.0 or lower. For details, see this topic on the Explorers Hub.

  • Adds support for akka http with Scala 2.13 #271

  • Class annotation to trace lambda methods #274

  • Class annotation to trace methods by return type #275

Fixes:

  • Fixes an issue that could cause multiple versions of akka-http-core instrumentation to apply at the same time. #208

  • The agent will now log dropped events at FINE instead of WARN to decrease verbosity. #296

  • Fixes Javadoc comments that incorrectly stated that, when calling the noticeError API multiple times, the first error would be reported when in fact it is the last error that is reported. #313

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.

Version 6.5.0 (2021-4-26)

New Features and Improvements:

  • The agent no longer bundles SSL certificates with it and the use_private_ssl option that configured the agent to use the previously bundled certificates has been removed. By default, the agent will use the SSL truststore provided by the JVM unless it is explicitly configured to use a different truststore with the ca_bundle_path option. See Configuring your SSL certificates for more details. (#245)

Fixes:

  • Fixes an issue that could cause incorrect transaction naming when using JAX-RS sub-resources. (#234)
  • Reactor Netty instrumentation improvements and fixes. (#237, #239, #243)

Deprecation Notice

  • Java 7 compatibility deprecation

In order to continue to innovate and efficiently provide new capabilities to our customers who run on the JVM, Java 7 support has been deprecated and this will be the last version of the agent compatible with it.

If you are running Java 7, you may continue to use Java agent 6.5.0 or lower.

For more information, see the Explorers Hub post.

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.

Version 6.4.0 (2021-1-27)

New Features and Improvements:

  • Spring Webflux/Netty Reactor instrumentation improvements for enhanced tracing across asynchronous thread hops (#174, #190, #195).
  • Infinite tracing will now utilize a backoff sequence on retries. (#180)
  • New distributed tracing APIs have been added to better support general use cases for propagating distributed tracing headers. In particular the new APIs provide enhanced support for W3C Trace Context but are flexible enough to support other header protocols. Previous distributed tracing APIs have been deprecated and are subject to removal in a future agent release. See documentation here. (#188)

Fixes:

  • Updated the Java agent’s snakeyaml dependency to 1.27. (#182)
  • In some environments the jar collector service could lead to high CPU utilization at application startup. The agent now provides a configurable rate limiter, with a reasonable default, for processing jars detected in the application’s environment. See documentation here. (#183)

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.

Version 6.3.0 (2020-12-17)

New Features and Improvements:

Fixes:

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.

Version 6.2.1 (2020-11-17)

Fixes an issue where Spring-Webflux applications with endpoints returning no or empty content could become unresponsive

Version 6.2.0 (2020-11-10)

New Features and Improvements:

    return serviceA.getData()
                .map(service -> Response.builder().service(service).build())
                .flatMap(serviceB::getData)
                .flatMap(serviceC::getData)
                .doOnNext(this::saveResponse);

Fixes:

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.

Version 6.1.0 (2020-09-30)

Version 6.0.0 (2020-08-26)

Version 5.14.0 (2020-07-27)

Final closed-source release.
See the external release notes.