Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Community Plus header

New Relic Dropwizard reporter

A Dropwizard metrics reporter for sending dimensional metrics to New Relic using the New Relic Java Telemetry SDK. For the juicy details on how Dropwizard metrics are mapped to New Relic dimensional metrics, please visit the exporter specs documentation repo.

How To Use




or if you're using kotlin build gradle...



If you do not want to depend on okhttp, you can remove the dependency on telemetry-http-okhttp, but you will need to construct a MetricBatchSender instance using its builder and provide your own implementation of the com.newrelic.telemetry.http.HttpPoster interface.

MetricBatchSender sender = MetricBatchSender.builder().httpPoster(<your implementation>);

Note: to use the sample code below, you will need the telemetry-http-okhttp library mentioned above. It provides implementations communicating via HTTP using the okhttp libraries, respectively.

Start the reporter

Early in the lifecycle of your application, you will want to create and start a NewRelicReporter.

The YOUR_SECRET_API_KEY is referring to your New Relic Event API insert key. For more information and how to obtain a key, visit our docs.

MetricRegistry metricRegistry = new MetricRegistry(); // If you're already using dropwizard-metrics you may already have one of these.
String apiKey = "<YOUR_SECRET_API_KEY>";
MetricBatchSender metricBatchSender = SimpleMetricBatchSender.builder(apiKey).build();

Attributes commonAttributes = new Attributes()
            .put("host", InetAddress.getLocalHost().getHostName())
            .put("appName", "Your Application Name Here")
            .put("other", "any other common attributes you wish");
NewRelicReporter reporter =, metricBatchSender)
reporter.start(15, TimeUnit.SECONDS);

Dropwizard integration

If you are using the actual Dropwizard REST framework, you can get a reference to the MetricRegistry from the Dropwizard Environment in order to register your reporter.
It might look something like this:

public class MyApplication extends Application<MyConfig> {

    public void run(MyConfig configuration, Environment environment) {
        MetricRegistry registry = environment.metrics();
        MetricBatchSender metricBatchSender = buildMetricBatchSender(); // see above for more complete example
        NewRelicReporter reporter =, metricBatchSender)
        reporter.start(15, TimeUnit.SECONDS);


Dropwizard Metrics Reporter

If you have a dropwizard project and have at least dropwizard-core 0.7.X, then you can perform the following steps to automatically report metrics to New Relic.

Add the following to your dropwizard YAML config file.

  frequency: 1 minute                       # Default is 1 second.
    - type: newrelic
      apiKey: <YOUR_SECRET_API_KEY>
      overrideUri:                          # Optional. Defaults to
      disabledMetricAttributes:             # Optional. Defaults to (none)
      commonAttributes:                     # Optional. Defaults to (none)
      includes:                             # Optional. Defaults to (all).
      excludes:                             # Optional. Defaults to (none).

Once your dropwizard application starts, your metrics should start appearing in New Relic.

Javadoc for this project can be found here: Javadocs


CI builds are run on Azure Pipelines: Build Status The project uses gradle 5 for building, and the gradle wrapper is provided.

To compile, run the tests and build the jars:

$ ./gradlew build

Find and use your data

For tips on how to find and query your data, see Find metric data.

For general querying information, see:

Release Process

Publish to Staging Repo

To stage the release simply submit and merge a PR to update the build.gradle.kts file with the version to be released (e.g. version := "0.5.0").

Results of the job can be viewed here: After the staging release job has run successfully it will publish the new artifact to a staging repository on Sonatype at:

Manually Release Staging Repo

  1. Find the staging repo on Sonatype, which should be named similar to comnewrelic-nnnn, and validate that the contents and version look correct.
  2. If the contents look correct, select the staging repo and choose close, leaving a comment such as releasing 0.5.0.
  3. When the staging repo is finished closing, select the staging repo and choose release, keeping the Automatically Drop checkbox checked, and leave a comment such as releasing 0.5.0.
  4. Verify that the artifact was published on Maven Central at:

Post Release

Submit and merge a PR with the following:

  • Update the build.gradle.kts file with to a snapshot version of a potential future release (e.g. version := "0.5.1-SNAPSHOT").
  • Update the CHANGELOG with details of the new release:
    ## [0.5.0]
    - Miscellaneous bug fixes and tweaks
  • Update the Usage example in the README with the newly released version (e.g. implementation("com.newrelic.telemetry:dropwizard-metrics-newrelic:0.4.0")).


New Relic hosts and moderates an online forum where customers can interact with New Relic employees as well as other customers to get help and share best practices. Like all official New Relic open source projects, there's a related Community topic in the New Relic Explorers Hub. You can find this project's topic/threads here:


We encourage your contributions to improve the New Relic Dropwizard reporter! Keep in mind that when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project.

If you have any questions, or to execute our corporate CLA (which is required if your contribution is on behalf of a company), drop us an email at

A note about vulnerabilities

As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.

If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.

If you would like to contribute to this project, review these guidelines.


The New Relic Dropwizard reporter is licensed under the Apache 2.0 License.