Version 6.4.2

Fixes an issue that could cause some instrumentation modules (e.g. jax-rs-1.0) to have a WeaveViolation and not apply properly.

Version 6.4.1

• Fixes an issue with a race condition in the Infinite Tracing Span Observer. The issue could lead to dropped spans. #206

Version 6.4.0

🚨 There is an issue with this agent release that could lead to spans not being sent to Infinite Tracing. Please use 6.4.1 instead. (#206)

Note:

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 that may be supported by the agent in the future. Previous distributed tracing APIs have been deprecated and are subject to removal in a future agent release. See documentation here. (#188)
  • Transaction.insertDistributedTraceHeaders(Headers) is used to create and insert distributed tracing headers (both newrelic and W3C Trace Context) into a Headers data structure.
  • Transaction.acceptDistributedTraceHeaders(TransportType, Headers) is used to accept the distributed tracing headers sent from the calling service and link these services together in a distributed trace.

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

New Features and Improvements:

• Adds support for Spring Webflux 5.3.+.
• Adds configuration for ignoring netty reactor errors. The relevant configuration property is reactor-netty.errors.enabled. Error reporting is enabled by default.
• Adds support for Scala 2.13, including Akka Http and Play. Thank you junder31 for these contributions.

Fixes:

• The netty-4.0.8 instrumentation would sometimes not start a Transaction on channelRead, potentially affecting instrumentation dependent on it including: Spring, Akka and Play.
• Updates the Java agent’s Apache HttpClient dependency to 5.13.
• Spring Webclient could report the wrong URL when multiple HTTP calls to several URLs occurred in parallel. Thank you veklov for contributing this fix.

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

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

Version 6.2.0

New Features and Improvements:

• Support for Real Time Profiling of your JVMs. The agent can now run in parallel with the JFR Daemon to provide Realtime Profiling of your JVMs using Java Flight Recorder! Read more about it in our blog and documentation.
• The agent now supports parsing cgroup ids that do not contain docker-. Previously, the agent only supported docker cgroup ids that contained docker- in them, such as 1:cpu:/system.slice/docker-12345abcde.scope. The agent now supports parsing cgroup ids such as 1:cpu:/system.slice/crio-12345abcde.scope.
• Adds support for Akka Http Core 10.2.0. Thank you jobicarter for reporting this issue.
• Adds support for gRPC 1.30.0. Thank you jef for submitting this request and trying it out.
• Adds support for map and flatmap async external calls in spring webflux framework. Previously the agent didn’t support client calls that occurred within the map or flatmap methods within the spring webflux framework. External calls such as serviceB and serviceC in the example below would not get reported to New Relic:

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

• Adds support for Play 2.16.3. Many thanks to junder31 for this contribution.

Fixes:

• Prevents the agent from logging a timeout exception when using New Relic Edge with Infinite Tracing but the agent hasn’t sent spans in a while.
• Prevents the agent from logging a socket exception when trying to retrieve cloud provider information in a non-cloud environment.
• Adds New Relic EU certifications if ca_bundle_path is specified.
  This fix also came with the reintroduction of the use_private_ssl config, which can be set to add our agent certs to the truststore.

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

• Support for Java 15
• Ability to add attributes to segments
• Newrelic.addCustomParameter() API now supports boolean values
• Fix a config issue where the agent would try to read environment
  variables using system-property syntax. It will now log the correct syntax and ignore the incorrect config
• The Java agent now includes the newrelic.com SSL certificate.
  In previous agent versions, applications using a custom Truststore would have to provide their certificate or use the
  use_private_ssl configuration which was removed in 6.0.0.
• Fixed an issue where applications could fail to start due to the agent attempting to access the JMX MBean server before it was initialized.

Version 6.0.0

• Fix for asynchronous jar file collection. Collection of modules will no longer block the initial first harvest.
• Fix for Real Time Streaming. The first Real Time Streaming harvest will no longer be delayed by 30 seconds.
• Support for okhttp 4.4 instrumentation.
• Fix for reactor-netty verifier versions
• Improve reconnect behavior by not pinning to preconnected collector host instance.
• Fix race condition around connection pool exhaustion by separating pool timeout from connection timeout.
• Register an MBean to expose the agent linking metadata.
• Note: This release removed the certificate bundle from the agent artifact. Users previously using use_private_ssl should now use the ca_bundle_path configuration directive