Algolia

    New Relic Integration

    Send Load Test Metrics to New Relic

    The New Relic integration sends the metrics of every LoadFocus test that uses it to your New Relic account over OpenTelemetry (OTLP). You can then look at load test results next to your APM, infrastructure and log data, and see how your application behaves while it is under load. It works with cloud tests, JMeter tests and k6 tests.

    New Relic Integration form in LoadFocus with the name, region and license key fields

    What You Need

    • A New Relic account. The free tier works.
    • An ingest license key. In New Relic, open your user menu, go to API keys, and copy or create a key of type INGEST - LICENSE. User keys (they start with NRAK-) cannot send data.
    • Your data region, US or EU. EU license keys start with eu01.

    Create the Integration

    1. Open Account settings > Integrations, or go to the Integrations page.
    2. Click New Integration and choose New Relic.
    3. Enter a name, paste the license key and check the region. A key that starts with eu01 switches the region to EU for you.
    4. Click Save integration.

    LoadFocus checks the key with New Relic before it saves the integration. If New Relic rejects it, the form tells you so under the key field. That almost always means the key is not an INGEST - LICENSE key, or it belongs to the other region.

    Attach the Integration to a Test

    1. Open a cloud, JMeter or k6 test.
    2. In Integration Configuration, select your New Relic integration.
    3. Save or run the test.

    Every run that uses the integration shows Exports to: New Relic in the configuration panel of its results page.

    What You Will See in New Relic

    Metrics arrive as dimensional metrics (the Metric data type) with these attributes on every data point:

    • service.name: loadfocus-jmeter for cloud and JMeter tests, k6 for k6 tests
    • loadfocus.testrunname and loadfocus.testrunid: the test and the run they came from

    Cloud and JMeter tests send three metrics:

    • jmeter.samples: the number of requests, with the attributes sampler (the request label) and status (ok or ko)
    • jmeter.response_time_ms: response times as a histogram, per sampler
    • jmeter.errors: failed requests, per sampler and response_code

    k6 tests send k6's standard metrics, such as http_reqs, http_req_duration, iterations and vus.

    To see what arrived, open Query your data in New Relic and run:

    FROM Metric SELECT count(*) WHERE service.name IN ('loadfocus-jmeter', 'k6') SINCE 1 hour ago FACET metricName LIMIT MAX

    Requests, errors and response times per test run:

    FROM Metric SELECT sum(jmeter.samples), sum(jmeter.errors), average(jmeter.response_time_ms), percentile(jmeter.response_time_ms, 95) WHERE service.name = 'loadfocus-jmeter' SINCE 1 hour ago FACET loadfocus.testrunname

    Metrics are sent with delta temporality and gzip compression, which is what New Relic recommends for OTLP.

    Troubleshooting

    • The form says the key was rejected: use an INGEST - LICENSE key, not a user key, and make sure the region matches your New Relic account. An EU key sent to the US endpoint is rejected, and so is the reverse.
    • Nothing shows up in New Relic: for cloud and JMeter tests, open the run's Logs tab and look at the JMeter log. The last lines include Metrics export to otlp.nr-data.net: N of M batches accepted (or otlp.eu01.nr-data.net). If an export failed, the first failure is logged with its HTTP status.
    • An integration created before September 24, 2026: open it, paste the license key again and save it. Integrations saved before that date do not send data.
    • The run itself is never affected: if an integration is misconfigured, the test still runs. It just exports no metrics.

    Edit or Remove the Integration

    • Edit: click the edit icon on the integration in Integrations. For security, the license key is never shown again, so paste it every time you save.
    • Remove: click the delete icon. Tests that used it stop exporting.
    Previous
    Dynatrace Integration
    Next
    OpenTelemetry (OTLP) Integration