Migrate to NRQL

List metric names for your app

To view the metric names available for your application:

SELECT uniques(metricTimesliceName) FROM Metric WHERE appId = '$APP_ID' AND newrelic.timeslice.value IS NOT NULL SINCE 30 MINUTES AGO LIMIT MAX

You can also filter using the application name:

SELECT uniques(metricTimesliceName) FROM Metric WHERE appName = '$APP_NAME' AND newrelic.timeslice.value IS NOT NULL SINCE 30 MINUTES AGO LIMIT MAX

Or using a specific agent (host):

SELECT uniques(metricTimesliceName) FROM Metric WHERE realAgentId = '$AGENT_ID' AND newrelic.timeslice.value IS NOT NULL SINCE 30 MINUTES AGO LIMIT MAX

Get your app's metric timeslice data values

The REST API v2 accepts a list of metric names and a list of values to fetch metric timeslice data.

The metric names are the same, you can filter them with the metricTimesliceName field in your NRQL query.

Each API value can be mapped to a NRQL function, you can refer to the table below.

Example, for the following API request:

$
curl -X GET "https://api.newrelic.com/v2/applications/${APP_ID}/metrics/data.json" \
>
     -H "X-Api-Key:${API_KEY}" -i \
>
     -d 'names[]=HttpDispatcher&values[]=average_call_time&values[]=call_count'

You would use the following query:

SELECT COUNT(newrelic.timeslice.value) AS call_count, average(newrelic.timeslice.value) * 1000 AS average_call_time
FROM Metric
WHERE appId = $APP_ID AND metricTimesliceName = 'HttpDispatcher'

If the function includes $TIME_WINDOW_IN_SECONDS, it means that you need to replace it with the time window you want to query.

Example, if you query a 30 minutes time window, you would replace $TIME_WINDOW_IN_SECONDS with 1800.

Apdex metrics

EndUser & Mobile metrics

These metrics will return the same result as what you would get from the REST API v2, but some results may differ from what you see on the New Relic UI. This is because the UI uses events instead of timeslice data. If you want to get the same results as the UI, you should query the events directly.

Timeseries and summaries

By default, the REST API returns a series of metric data values based. To obtain the average of these values, you would include &summarize=true in your API call.

In NRQL, that's the opposite. You get a summary by default, and you can get the timeseries by adding TIMESERIES to your query.

Another difference is that the default time window of the REST API is 30 minutes, while in NRQL, it is 1 hour.

Query multiple metrics

You can still query multiple metrics at once with NRQL, here's an example:

SELECT
    FILTER(1000 * AVERAGE(newrelic.timeslice.value), WHERE metricTimesliceName = 'HttpDispatcher') as average_response_time,
    FILTER(count(newrelic.timeslice.value), WHERE metricTimesliceName = 'Errors/all') as error_count,
    FILTER(average(newrelic.timeslice.value), WHERE metricTimesliceName = 'Memory/Heap/Max') as used_mb_by_host
FROM Metric
WHERE appName = '$APP_NAME'
SINCE 1 day ago