Skip to content

Latest commit

 

History

History
712 lines (517 loc) · 51.9 KB

CHANGELOG.md

File metadata and controls

712 lines (517 loc) · 51.9 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.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

Fixes

  • Prevented a NullPointerException from the lettuce instrumentation newrelic#1204

  • Fix failure with browser agent auto injection for tomcat versions 8.5.87+ and 9.0.74+ newrelic#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/<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 newrelic#1145
  • Ensure that TokenAndRefCount.token is never null newrelic#1148
  • Correct a possible NullPointerException being thrown when calling addCustomAttributes newrelic#1141
  • Fix ClassCircularityError when agent attaches newrelic#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

Fixes

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

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 http.responseCode, 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 http.responseCode, 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 http.responseCode, 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.