Java Release Notes

Recent Java agent release notes are listed below. If you would like a release that has been used extensively with a list of known issues, see Established releases (Java) for download link and version information.

Wednesday, June 26, 2019 - 08:15 Download

Improvements

  • MongoDB

    This release adds instrumentation for mongo-java-driver clients created using the MongoClients class Previous versions of the agent only supported the MongoClient() constructor Note: The MongoDB Asynchronous Java Drivers are not yet supported.

  • Custom request header attributes

    The Java agent now provides a new configuration option to report HTTP request header(s) as transaction attributes. See the documentation for more details.

  • Distributed tracing

    Datastore span events now include a db.collection attribute. This field represents the collection or primary table name for the associated query. It is accessible in Insights, Distributed Tracing, and anywhere you get your favorite spans.

  • GC Time

    The Java agent now records time spent waiting for garbage collection during the duration of a transaction and includes the GC time on the corresponding transaction trace as well as the transactions time chart.

    This setting is configurable as follows in the newrelic.yml:

  transaction_tracer:
    gc_time_enabled: true 

Fixes

  • Fixes an issue where very long-running transactions with a large number of segments would cause an excessive amount of memory usage. The agent will no longer trace segments once the segment_limit has been reached.
Thursday, June 13, 2019 - 17:15 Download

Fixes

  • gRPC

This release fixes two bugs in the Java agent's gRPC instrumentation. We highly recommend customers using gRPC instrumentation to upgrade to this and or later agent versions.

  • References to transaction segments were not being removed correctly, which can cause a memory leak
  • The agent could cause the gRPC server listeners to fail to execute its completed and/or cancelled methods, which can cause unexpected behavior
Wednesday, May 29, 2019 - 09:44 Download

Improvements

  • JAX-RS

    This release adds support for @PATCH JAX-RS annotation. The agent will create and name transactions based @PATCH annotations.

Fixes

  • Fixes an issue in the Scala instrumentation that would cause an Java.lang.IllegalArgumentException: to be thrown when the Lightbend Cinnamon agent is in use.

  • Fixes an issue where Cross Application Tracing headers were incorrectly parsed when Distributed Tracing is enabled. Applications that use both Distributed Tracing and Cross Application Tracing will no longer report external transaction breakdown metrics.

  • Fixes an issue where the agent’s Kafka instrumentation would report WakeupExceptions as errors in New Relic. These exceptions will no longer be reported.

  • Fixes a Log4J ClassCastException for applications running on the IBM J9 JVM that set a custom logging manager via the -Djava.util.logging.manager system parameter.

  • The agent now supports using the thread profiler when the send_environment_info configuration is disabled.

Notes

  • The agent now sends data to New Relic using gzip compression by default. To use the previous compression set the compressed_content_encoding configuration value to deflate

  • The jdbc-resultset instrumentation is now disabled by default in the newrelic.yml and will be disabled by default in all future releases.

Known Issues

Fixed in 5.1.1

  • gRPC

This release contains two bugs in the Java agent's gRPC instrumentation. We highly recommend customers using gRPC instrumentation to upgrade to this and or later agent versions.

  • References to transaction segments were not being removed correctly, which can cause a memory leak
  • The agent could cause the gRPC server listeners to fail to execute its completed and/or cancelled methods, which can cause unexpected behavior
Wednesday, April 24, 2019 - 10:17 Download

Improvements

gRPC

The Java agent now supports gRPC. You will now see transactions, errors, external calls, and distributed traces for all of your gRPC-based clients and services.

Vert.x-3.7

The Java agent now supports Vert.x 3.7. The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client.

OkHttp 3.14.0

This release adds support for OkHttp 3.14.x. You will now see OkHttp 3.14 calls as external calls in New Relic.

spray-can

The Java agent now supports the spray-can client. The agent will now capture outbound http calls made with the spray-can client and report them as external calls and/or distributed traces.

Embedded Derby 10.15.1.3

The Java agent has expanded support for Derby JDBC up to and including version 10.15.1.3.

JVM monitoring

The Java agent now reports JMX stats for off-heap direct byte buffers. These metrics are available via the JVM page

recordCustomEvent API

The recordCustomEvent API has been updated to accept Map<String,?> as a second parameter instead of Map<String,Object>, allowing maps such as Map<String,String> to be passed without having to cast the type of the map's value.

Fixes

  • The agent no longer requires a newrelic.yml even when the app_name and license_key configuration options are set via environment variables and/or system properties. For more information, see the Java environment variables documentation.
  • HttpSessions JMX metrics were not reporting for Websphere Liberty Profile applications.
  • The transaction_events.max_samples_stored configuration value in the newrelic.yml would incorrectly override the system properties or environment variable values.
  • Applications running on WildFly 12 - 15 would fail start with NoClassDefFound errors for Java agent classes.
  • Play applications where external calls inside of future callbacks using async-http-client would not be recorded.
  • Setting log_limit_in_kbytes would result in the agent not logging to the agent log file if log_file_count was also set to less than 2.
  • Webflux status codes which were not recognized by Spring Webflux caused a 500 status code to be returned and an exception in application logs.

Known Issues

gRPC: Fixed in 5.1.1

This release contains two bugs in the Java agent's gRPC instrumentation. We highly recommend customers using gRPC instrumentation to upgrade to this and/or later agent versions.

  • References to transaction segments were not being removed correctly, which can cause a memory leak.
  • The agent could cause the gRPC server listeners to fail to execute its completed and/or cancelled methods, which can cause unexpected behavior.

Deprecation Notes

Self installer

The New Relic Java agent's self-installer has been removed in order to provide a more consistent user experience. To install the Java agent, add the full path to the newrelic.jar to the -javaagent flag in your JVM options. For more information on installing the agent on specific application servers, Docker, Maven, or Gradle, see the JVM argument documentation.

Deprecated instrumentation

The following instrumentation modules have been moved out of the default Java agent, and are now provided as a separate download. To continue using these modules, just add them to the agent's extensions directory in your newrelic folder or wherever your extensions directory is configured.

Wednesday, March 27, 2019 - 07:47 Download

Fixes

  • Fixed an issue where an exception would be thrown during agent initialization which caused the application to shut down when the log file is not writable. In previous agent versions there was an undocumented behavior where the agent would log to STDOUT instead.

  • Fixed a regression where a NullPointerException would be logged and instrumentation would not be applied when using an XML extension with comments preceding the instrumentation section.

  • Fixed issue where setting the log_limit_in_kbytes greater than 0 and log_file_count equal to 1 would result in the agent not logging to the agent log file.

Wednesday, March 20, 2019 - 07:33 Download

Improvements

  • Kafka-clients

    The Java agent now supports the kafka-clients library. The agent will automatically report up Kafka metrics to New Relic.

    Optional support is provided for reporting Kafka metrics as Insights events and for enabling distributed tracing. More information can be found in the New Relic documentation.

  • Java 12, Coretto and Zulu

    The New Relic Java agent is now fully compatible with Java 12. This release also adds support for the Amazon Coretto and Azul Zulu JDKs.

New APIs

  • Added ignoreErrors() to the Transaction API, allowing all errors reported within a specific transaction to be ignored.

  • Added addCustomParameters(Map<String, Object>) API, allowing multiple custom parameters to be added to a transaction at once.

  • Updated the noticeError() API documentation to clarify that when the api is invoked multiple times while in a transaction, only the first error will be reported.

Deprecated APIs

  • The custom transport channel API is now deprecated in favor of the Distributed Tracing API.

  • The skipTransactionTrace attribute on the @Trace annotation is now deprecated. The excludeFromTransactionTrace attribute should be used in its place.

Deprecated Instrumentation

  • JetS3t

    Removed built-in instrumentation for JetS3t. The agent will continue to report external calls made with the JetS3t client.

Fixes

  • Fixed an issue with Jax-RS subresource transaction naming where the root path is duplicated when a nested resource structure is used. This could lead to transactions being named incorrectly for incoming requests to a Jax-RS framework.

  • Fixed a bug in the agent's Jetty metric sampling that could prevent Jetty specific metrics from being reported when the number of threads returned by JMX is zero.

  • Fixed a NullPointerException that can occur when cross application tracing configuration is explicitly disabled.

  • Fixed an issue where transactions would be named incorrectly when using custom Akka Http stream directives or a pathEnd directive followed by a Segment directive.

  • Fixed an issue where certain usages of Akka and Scala would prevent transactions from being reported to New Relic. This would also manifest as a NullPointerException in the agent log at finest level.

  • The Java agent no longer includes Jaxb or Logback dependencies. A new dependency on Log4j2 has been added

Tuesday, February 12, 2019 - 10:29 Download

Improvements:

  • Vert.x 3.6

    The Java agent now provides visibility into your applications built using the Vert.x 3.6. The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client.

  • Wildfly 12-15

    The agent now supports Wildfly versions 12 through 15

Fixes:

  • Fixes an issue where applications using neo4j bolt JDBC driver could fail to start.
  • "log_daily" configuration did not respect documented precedence
  • Fixes a bug that caused the Spring Webflux instrumentation to fail to apply for spring-webflux versions greater than 5.0.*
  • Fixes an issue where transactions would not be fully reported if distributed_tracing.enabled = true and cross_application_tracer.enabled = false
  • Fixes an issue where Akka Http application would not start with the agent attached when using sbt
  • Fixes an issue where the agent could fail to determine the Hostname

Known Issues

Fixes in 4.12.0

  • Fixed an issue with Jax-RS subresource transaction naming where the root path is duplicated when a nested resource structure is used. This could lead to transactions being named incorrectly for incoming requests to a Jax-RS framework.
  • Fixed a bug in the agent's Jetty metric sampling that could prevent Jetty specific metrics from being reported when the number of threads returned by JMX is zero.
  • Fixed a NullPointerException that can occur when cross application tracing configuration is explicitly disabled.
  • Fixed an issue where transactions would be named incorrectly when using custom Akka Http stream directives or a pathEnd directive followed by a Segment directive.
  • Fixed an issue where certain usages of Akka and Scala would prevent transactions from being reported to New Relic. This would also manifest as a NullPointerException in the agent log at finest level.
  • The Java agent no longer includes Jaxb or Logback dependencies. A new dependency on Log4j2 has been added

Fixes in 4.12.1

  • Fixed an issue where an exception would be thrown during agent initialization which caused the application to shut down when the log file is not writable. In previous agent versions there was an undocumented behavior where the agent would log to STDOUT instead.
  • Fixed a regression where a NullPointerException would be logged and instrumentation would not be applied when using an XML extension with comments preceding the instrumentation section.
  • Fixed issue where setting the log_limit_in_kbytes greater than 0 and log_file_count equal to 1 would result in the agent not logging to the agent log file.

Fixes in 5.0.0

  • The agent no longer requires a newrelic.yml even when the 'app_name' and 'license_key' configuration options are set via environment variables and/or system properties. For more details please see: https://docs.newrelic.com/docs/agents/java-agent/configuration/java-agen...
  • HttpSessions JMX metrics were not reporting for Websphere Liberty Profile applications
  • The transaction_events.max_samples_stored configuration value in the newrelic.yml would incorrectly override the system properties or environment variable values
  • Applications running on Wildfly 12 - 15 would fail start with NoClassDefFound errors for Java agent classes.
  • Play applications where external calls inside of future callbacks using async-http-client would not be recorded.
  • Setting log_limit_in_kbytes would result in the agent not logging to the agent log file if log_file_count was also set to less than 2
  • Webflux status codes which were not recognized by Spring Webflux caused a 500 status code to be returned and an exception in application logs.

Fixes in 5.1.0

  • Fixes an issue in the Scala instrumentation that would cause an Java.lang.IllegalArgumentException: to be thrown when the Lightbend Cinnamon agent is in use.
  • Fixes issue where Cross Application Tracing headers were incorrectly parsed when Distributed Tracing is enabled. Applications that use both Distributed Tracing and Cross Application Tracing will no longer report external transaction breakdown metrics.
  • Fixes an issue where the agent’s Kafka instrumentation would report WakeupExceptions as errors in New Relic. These exceptions will no longer be reported.
  • Fixes a Log4J ClassCastException for applications running on the IBM J9 JVM that set a custom logging manager via the -Djava.util.logging.manager system parameter.
  • The agent now supports using the thread profiler when the send_environment_info configuration is disabled.

Fixes in 5.2.0

  • Fixes an issue where very long-running transactions with a large number of segments would cause an excessive amount of memory usage. The agent will no longer trace segments once the segment_limit has been reached.
Wednesday, January 23, 2019 - 10:00 Download

Improvements

  • This release adds Transaction event attributes that provide context between your Kubernetes cluster and services. For details on the benefits (public beta coming soon) see this blog post.
  • The Java agent now supports setting all configuration options via Environment variables. Environment variables will take precedence over newrelic.yml but cannot be updated dynamically since they are read statically on application startup.
  • Adds instrumentation for the Akka HTTP client, versions 10.0 to 10.1.x. This client is used via the Http().singleRequest() method and the agent will now automatically capture these requests as External metrics.
  • Support for MySQL connector 8.0.x
  • Adds official support for Akka Http 10.1.6
  • Span event attributes can now be filtered using include / exclude rules.
  span_events:
    enabled: true
    attributes:
      include:
      exclude:
  • Rename transaction trace segment parameter key from uri to http.url and rename trace key from database_name to db.instance.

Fixes

  • Fixes an issue where Akka HTTP instrumentation can cause higher than normal memory usage when an async Directive is used in the route for an Akka HTTP based app. This can also result in mis-named transactions for any paths underneath the custom Directive.
Tuesday, December 18, 2018 - 13:46 Download

Improvements

  • The 'request.uri' attribute is now included in Transaction events and corresponding Transaction Error events. As a result this attribute can now be queried in Insights. It may be excluded via the exclude list in the attributes stanza of the yaml config file. It is also excluded when High Security Mode is enabled.
  • Distributed Tracing can now be enabled at the same time as auto app naming. Each application created by this setting will share an event reservoir for Distributed Tracing.
  • Updates Akka HTTP instrumentation to support the newest version of Akka HTTP, 10.1.5 and above.

Fixes

  • Fixes a possible NullPointerException that could occur in Hystrix instrumentation and propagate into application code.
  • Fixes a bug where usage of the HttpsURLConnection getInputStream() method could cause some scoped external metrics to be double-counted.
  • Fixes an issue that prevents the agent from connecting to an HTTP proxy that does not requires a username or password.

    When configured to use an HTTP proxy by using proxy_host and proxy_port, the agent would look for proxy_username and proxy_password. If those weren't provided, the agent would use an empty string for proxy_username and proxy_password.

  • Prevents unnecessary dependencies from showing up in the newrelic-agent pom
  • Fixes deadlocks occurring in agent 4.7.0 that were caused by instrumentation of classes in the sun/nio/cs/.* package
  • Fixes an issue where custom jmx metrics with '.'s in the attribute name would not get recorded.
Tuesday, November 13, 2018 - 09:22 Download

Fixes

  • Fixed an issue where the agent would break webpage rendering by inserting New Relic Browser monitoring javascript into the <header> tag of pages which were missing <head> tags.

  • Certain frameworks, like Spring Cloud Gateway, triggered a bug in the Spring webflux instrumentation, causing transactions to stay open until they timed out. This bug resulted in more memory pressure and looked like a memory leak. This has been fixed in this release.

  • Fixed an issue where the agent would stop reporting to New Relic following a ForceDisconnectException and accumulate transaction data resulting in OutOfMemory Exceptions.

  • The agent now validates that app_names only contains three application names. If the agent is configured to report more than three application names, the agent will log a warning message and stop reporting to New Relic.

  • When a custom WSRequestFilter is used that modifies an outbound play-ws request, the agent would report overly long segments due to Segment timeouts and will also result in a loss of External/ metrics. This has been fixed.

Wednesday, October 3, 2018 - 08:52 Download

Improvements

  • Java 11

The New Relic Java agent is now fully compatible with Java 11. For more on JDK releases and the Java agent, see this topic on the Explorer's Hub.

  • Solr 7.0 JMX Metrics

The Java agent now collects JMX metrics for Solr 7.0

Monday, September 24, 2018 - 11:16 Download

Improvements

  • Spring 5

    The Java Agent now provides instrumentation for Spring 5 and Webflux. The agent will name transactions based on router functions as well as Spring controller and spring web annotations. The agent also provides support for Spring WebClient to capture external requests and timing.

    Spring 5 instrumentation works with Spring Boot, Tomcat, and Jetty.  

    Note if you have previously disabled Spring instrumentation: There is a new spring-4.3.0 instrumentation module that gets used in place of the previous spring-4.2.0 module for any customers running Spring 4.3.0 and above. If you had previously disabled support for spring-4.2.0 and you are running spring-4.3.0 you will want to change your class_transformer stanza in your newrelic.yml from:

    class_transformer:
      com.newrelic.instrumentation.spring-4.2.0:
        enabled: false
    

    to:

    class_transformer:
      com.newrelic.instrumentation.spring-4.3.0:
        enabled: false
    

Fixes

  • Fixes an issue where the agent could cause an application deadlock when two tokens are created and linked from the other’s thread. This affects users of the New Relic token API and also users of the Hystrix framework.
  • Fixes an issue where the agent would not capture JMX Datasource information from Tomcat when JDNI GlobalNamingResources is used.

Known Issues

Transaction reporting to New Relic may be delayed by up to 10 minutes when Spring WebClient is used to create http requests that never execute.

Tuesday, September 4, 2018 - 09:41 Download

Improvements

  • Apache HttpAsyncClient

    The Java agent now provides instrumentation for Apache HttpAsyncClient 4.1+. You will see your HttpAsyncClient calls as externals in New Relic.

  • AsyncHttpClient

    The Java agent now provides instrumentation for AsyncHttpClient. You will now see the time spent in external service calls made using AsyncHttpClient in New Relic. If the external service is also running New Relic, you will see cross application tracing (CAT) details as well.

  • Vert.x 3.5

    The Java agent now provides visibility into your applications built using the Vert.x 3.5. The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client.

  • JBoss EAP 7

    The Java Agent now provides instrumentation for JBoss EAP 7. You will now see the same visibility into your web transactions, app server stats, and frameworks that you have with previous versions of JBoss EAP.

  • Play 2.7

    The Java Agent now provides instrumentation for Play 2.7. The previous Java agent release supports versions of Play up to 2.6.

  • WebSphere Liberty

    Added ThreadPool metrics for WebSphere Liberty Profile. You will now see the active threads in the Threads tab of the JVM metrics page

Fixes

  • Fixes an issue where OKHttp 3 was not tracking external total time correctly.
  • Fixes an issue where for some JDBC drivers, the agent would execute additional getMetaData queries..
  • Fixes an issue with the agent’s Scala instrumentation that could result in incorrect throughput, invalid or negative data in transaction segments, or inability to ignore status codes.
  • Fixes an issue with the play-ws instrumentation that caused ClassNotFound exceptions to occur in the agent logs when withHeaders is used. This could result incomplete transactions and attributes in RPM.
Wednesday, August 8, 2018 - 12:08 Download

Improvements

  • Java 10

The New Relic Java agent is now fully compatible with Java 10. For more on JDK release and the Java agent, see this topic on the Explorer's Hub.

  • Not compatible with Java 6

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 6. If you are running Java 6, you may continue to use Java agent 4.3.0 or lower. For details, see this topic on the Explorer's Hub.

  • Akka 2.5 and Akka HTTP 10.1

The Java agent now supports Akka 2.5.x and Akka HTTP 10.1.x. You will see your Akka HTTP calls as New Relic transactions, see the hand-offs between Akka actors, and understand the calls to other databases and services.

  • Solr 7

The Java agent now supports Solr 7.x. New Relic’s Solr support reports database calls to Solr servers as well as monitors the Solr server itself.

Known Issue: JMX stats collection for Solr 7 isn't supported as of this release.

  • WebLogic datasource

The Java agent now displays health data about WebLogic’s datasource in the Datasource tab under the JVM page.

Fixes

  • Fixed an issue where the Java agent 4.3.0 would not report data depending on the locale setting of the JVM. Java Agent 4.3.0 failed to send event data if the JVM locale is set to use a comma as the decimal. You would see NumberFormatException in the agent log.
  • Fixed a rare issue where the agent will incorrectly attempt to continually retransform classes when an extension with a modification date in the future is used, causing a significant increase in CPU load.
  • Fixed a ConcurrentModificationException caused by ning instrumentation that manifests in Mule instrumentation that causes the request it affects to be retried and the Java agent to not report header data.
  • Fixed an issue where if enable_auto_app_naming was set to true and distributed_tracing.enabled was set to true it would sample every distributed trace event. Now if the agent has both configs enabled, it will not turn on distributed tracing.
Tuesday, July 31, 2018 - 10:00 Download

Improvements

  • Distributed tracing

Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before.

Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide before you enable this feature.

To enable distributed tracing, set enabled to true in the distributed_tracing stanza in the newrelic.yml config file.


  distributed_tracing:
    enabled: true
  • Added configuration option proxy_scheme to allow the agent to connect via https only proxies.

Fixes

  • Fixed an issue where transaction throughput counts could be artificially inflated when using async servlets in Jersey.
  • Fixed an issue where JBoss and Wildfly datasources could cause a LinkageError.
Tuesday, June 12, 2018 - 14:24 Download

Bug fixes

  • Fixed a bug where transactions were being kept alive for too long when application is under heavy GC, causing inaccurate throughput to be reported.
  • Fixed a bug in which Akka routing instrumentation could cause extra memory usage. When this is the case, the transaction throughput will look significantly lower than anticipated.
  • Fixed a rare bug in Play WS instrumentation where exceptions thrown by instrumentation were propagated out to the application code, potentially causing the request to error.
  • Fixed a bug where Jersey Client and HttpUrlConnection could be double instrumented, resulting in inflated external call count.
  • Fixed a bug where the total time and response time for a long running task could be misreported.
Wednesday, May 2, 2018 - 16:46 Download

Improvements

  • Configuration for custom_insights_events.max_samples_stored format in YAML has been changed. For agents 4.1.0 and above, the old .yml config setting will be ignored, which will result in the agent defaulting to max samples stored of 10,000 custom events. When you update your agent, please migrate to the new format:

  custom_insights_events:
    enabled: true
    max_samples_stored: 5000
  • The agent will log a warning message when it detects that the java.endorsed.dirs property is used. Classes in these directories cannot be instrumented by the agent because they are loaded by the bootstrap classloader.

Fixes

  • Ensure that custom events added during a transaction do not get discarded if the transaction is ignored via a call to NewRelic.ignoreTransaction().
  • A security update that corrects an issue affecting PostgreSQL that could occur if High Security Mode was enabled (or record_sql was set to off) and a query ran slow enough to trigger an explain plan. If the above conditions were met the agent may not have properly stripped out all information from the query. For information on this fix, see the security bulletin.
  • Addresses cases where the agent could not parse database statements that included the IGNORE and INTO keywords.
Thursday, April 19, 2018 - 10:22 Download

Fixes

  • Fixes an issue Introduced in 3.48.0 with event sampling. The agent would only report the first max_samples_stored events in a given minute reporting period and disregard the remainder for that minute. With the fix, the agent randomly samples those events across the reporting period.
Wednesday, April 4, 2018 - 09:40 Download

Improvements

  • Removed the SSL configuration option: SSL is now always used in communication with New Relic servers. The newrelic.yml ssl configuration and -Dnewrelic.config.ssl system property are no longer used. Setting either value to anything other than true will result in logging a warning.
  • Minimum version required for use in EU datacenter.

Fixes

  • Fixes an issue where the thread profiler could fail to report. In this case, the agent logged a java.lang.StackOverflowError.
Monday, March 12, 2018 - 07:29 Download

Improvements

  • Customers using Tomcat, WebSphere Liberty, or Resin now have data source information available. Data source information includes the number of active and idle connections, as well as the maximum possible connections. This information can be seen under the Data Source tab on the JVMs page
  • CompletableFuture instrumentation is more efficient
  • Disabling SSL connections to New Relic has been deprecated. SSL connections are enabled by default. In a future release, the option to disable SSL will be removed.

Bug fixes

  • Fixed an issue that in rare cases prevented Play async transaction tracking
  • Fixed a memory leak that could occur in Spymemcached instrumentation
  • Fix to disable attributes.include lists when High Security Mode is enabled
  • Fixed an issue where errors outside of a transaction did not contain custom attributes on the event
  • Fixed an issue that caused the UI to not display errors that had error messages over 255 bytes

Pages