New Relic, Inc. is an American web tracking and analytics company based in San Francisco. The company's cloud-based software allows websites and mobile apps to track user interactions and service operators' software and hardware performance.

Although we do not have a dedicated New Relic integration, this example will show how you can send test results data from your UXI dashboard to New Relic using the Generic HTTP Endpoint Data Push Destination using New Relic.

Note: The data sent to New Relic will be stored as JSON logs and visible through the logs UI.

To Get Started

Obtain an Ingest - License key from your New Relic account under API Keys:

Create a key and save the value. You can refer to the New Relic documentation here for more information.

Ensure you are using the correct Logs API endpoint for either the US or EU data center. Make sure to include the Ingest - License key as a URL parameter. For example, using the EU data center:

https://log-api.eu.newrelic.com/log/v1?Api-Key=YOUR_INGEST_API_KEY_HERE

Please see the documentation here for more information.

Next, open the UXI dashboard and navigate to Settings -> Integrations.

Under Data Push Destinations, Select Add Destination.

Enter the following in the menu.

Data Type: Test Results
Destination Type: Generic HTTP Endpoint
Name: Give the data push a unique, friendly name
URL: enter the URL for the New Relic API endpoint from the above step
Username: You can type anything here. Do not leave blank
Password: You can type anything here. Do not leave blank

Select Submit.

After a few minutes, you should see the test results in the New Relic logs UI. Below is an example dashboard that could be built using NRQL queries (see the dashboards documentation here)

Example New Relic Queries

An example query to get the average ping latency grouped by target:

FROM Log
SELECT average(latency_milliseconds)
WHERE code = 'PING'
FACET target LIMIT MAX
TIMESERIES 5 minutes since 1 hour ago

2. HTTP request time by interface type:

SELECT average(request_time_milliseconds)
FROM Log
WHERE code = 'HTTP_GET'
FACET context.interface_type
SINCE 60 minutes AGO

3. Critical connection and service events:

SELECT timestamp, context.hierarchy_node_name as Branch,
  code as Code, context.service_name as 'Service Name',
  target as 'Target', packets_dropped as 'Packets Dropped',
  request_time_milliseconds as 'Request time (ms)',
  latency_milliseconds as 'Latency (ms)',
  jitter_milliseconds as 'Jitter (ms)',
  dora_time_milliseconds as 'Dora (ms)'
FROM Log
WHERE code IN ('HTTP_GET', 'PING', 'VOIP_MOS', 'DHCP') OR packets_dropped > 0
LIMIT 50 SINCE 60 minutes AGO

4. Recent Alarms:

SELECT latest(Status), latest(Site), latest(Severity),
  latest(Description), latest(Start), latest(`End`),
  latest(if(numeric(Tim) < 0, '-', string(Tim, precision:2))) as 'Time to resolve',
  latest(Details)
FROM (FROM Log
  SELECT latest(status) as Status,
    latest(context.hierarchy_node_name) as Site,
    latest(severity) as Severity,
    latest(description) as Description, earliest(timestamp) as Start,
    latest(if(status = 'RESOLVED', timestamp, '-')) as 'End',
    (latest(if(status = 'RESOLVED', timestamp, 0)) - earliest(timestamp))/60000 as Tim,
    earliest(details) as Details
  FACET notification_reference limit MAX
) FACET notification_reference
since 1 days ago limit 1000

Example New Relic Alert

Use the query below to build an anomaly alert on average ping latency for each individual UXI sensor:

SELECT average(latency_milliseconds)
FROM Log WHERE code = 'PING'
FACET context.hierarchy_node_name

See the example screenshots below:

Creating Metrics from the Log data

You can use the New Relic events to metrics functionality to create long-term metrics from the Log data. See the documentation here. An example NerdGraph API request to create metrics for ping latency:

mutation {
  eventsToMetricsCreateRule(
    rules: {
      name: "network.ping.latency"
      description: "Created by Fred on November 27, 2025. Used by team Network."
      nrql: "FROM Log SELECT distribution(latency_milliseconds) AS 'network.ping.latency' WHERE code = 'PING' FACET target, context.hierarchy_node_name as node_name"
      accountId: YOUR_ACCOUNT_ID_HERE
    }
  ) {
    successes {
      id
      name
      nrql
      enabled
    }
    failures {
      submitted {
        name
        nrql
        accountId
      }
      errors {
        reason
        description
      }
    }
  }
}

An example query using the resultant long-term metric to give the average and 75th percentile latency by target and node name:

SELECT average(`network.ping.latency`),
  percentile(`network.ping.latency`, 75)
FROM Metric
FACET node_name, target

Data Push Destinations Example Using the Generic HTTP Endpoint with New Relic

To Get Started

Example New Relic Queries

Example New Relic Alert

Creating Metrics from the Log data