Java agent incubator

New Relic's Java agent Incubator is a program for experimental new instrumentation. It allows you to get visibility into frameworks that are not instrumented automatically by the New Relic agent.

If you have any feedback, questions, or problems with this instrumentation, create a post in the New Relic Online Technical Community and tag your post with java_incubator.

Installation

Specific instrumentation modules work with the latest Java agent version. To install the instrumentation:

  1. In the directory where the newrelic.jar and newrelic.yml are located, create a directory named extensions if there is not already one there.
  2. Copy the downloaded incubator module jar file into the extensions directory.
  3. Restart your server.
  4. Send some traffic to the server that will exercise the instrumentation.

Incubating modules

Instrumentation modules from New Relic are subject to the New Relic Java agent licenses, which are included in each module jar's LICENSE file.

Download the module

Allows New Relic trace annotations to be added to Clojure function metadata. Example: (defn ^{:newrelic-method-annotations {Trace {:dispatcher true}}} your-function [] ...) Trace is the annotation from the New Relic api.

Download the module

This instrumentation package intercepts org.apache.camel.component.http.CamelServlet.resolve and uses org.apache.camel.component.http.HttpConsumer.getPath() to name the transaction so that Web transactions have a finer grained name than the Camel servlet name.

View the bytecode with the terminal command javap -verbose -cp camel-2.12-<FILENAME>.jar org.apache.camel.component.http.CamelServlet.

Download the module

This instrumentation package requires the New Relic Java agent version 3.12.0 or higher. It samples C3P0 connection pools and reports busy and idle counts in metrics that start with Custom/Database Connection/C3P0

Download the module

This instrumentation package integrates with the MetricRegistry and begins sampling the registered metrics every minute. Reported metrics are prefixed with "Custom/CodaHale/Metrics2/" and can be viewed through custom dashboards.

Download the module

This instrumentation package integrates with the MetricRegistry and begins sampling the registered metrics every minute. Reported metrics are prefixed with "Custom/CodaHale/Metrics3/" and can be viewed through custom dashboards.

Download the module

This instrumentation package requires the New Relic Java agent version 3.12.0 or higher. It samples HikariCP connection pools and reports busy and idle counts in metrics that start with Custom/Database Connection/HikariCP

Download the module

This instrumentation package requires the New Relic Java agent version 3.12.0 or higher. It samples HikariCP connection pools and reports busy and idle counts in metrics that start with Custom/Database Connection/HikariCP

Download the module

This instrumentation package requires the New Relic Java agent version 3.14.0 or higher. This instrumentation package instruments the Kafka Producer DefaultEventHandler which sends the messages to Kafka. In the Kafka Consumer, the fetch method in SimpleConsumer is instrumented. These metrics can be viewed under the Transaction tab. Topic JMX metrics are being pulled from the producer and consumer. These JMX metrics can be viewed in a custom dashboard

The messaging API relies on two-way communication between producers and consumers. If your producer does not receive acknowledgement from a consumer, like in a fire-and-forget pattern, the messaging API will not accurately reflect the interactions with message queue brokers.

For more help

Recommendations for learning more: