New Relic

The Blameless platform offers integration with New Relic that allows you to monitor metrics that can be consumed within the SLO module.

Getting Started​

The New Relic SLO integration adds a new APM integration to our SLO integrations suite. Blameless uses the following areas of the New Relic API specifically:

• Applications List
• Metrics Names
• Metric Data

Create and Copy the Blameless API Client token​

First, you need to create and copy an API token. Refer to the New Relic site for more information regarding their APIs.

Create the Blameless API Client token​

1. Select "Account Settings" in the upper right corner of the New Relic Home Page. A drop-down option list appears.
2. Select "API Keys" under the Integrations section on the left nav bar.
3. Click on the "Create REST API key".
4. Click on "Show" and copy the REST API key provided.

Activate the New Relic Integration​

1. Open or switch windows to the Blameless application.
2. Select the “Settings” (gear) icon.
3. Select the “Integrations” option, then the “Metrics” sub-option.
4. Click on the “Manage” button associated with the “New Relic” row to select the "New Relic" app from the Integration list.
5. Select the "Enable New Relic" slider to activate it.

Copy the Blameless API Client token​

1. Scroll down to the New Relic API token field.
2. Paste the copied New Relic API key in the text field.
3. Click the “Save” button.

New Relic Query Language (NRQL)​

SLIs created in Blameless’ SLO Manager, and fed from New Relic metrics are built using the New Relic Query Language (NRQL)--allowing a broad and flexible support for the versatile New Relic metric types (APM, Synthetics, etc.), across all SLI types (Availability, Latency, Throughput, and Saturation).

More information regarding NRQL is available here.

Confirming the Integration​

1. Select the SLO portal icon (target) on the Blameless web application navigation menu.
2. Create and define an SLO in the Blameless web application.
3. Click on the “New Relic” button under the Select Data Source label to choose “New Relic” "as the datasource.
4. Click on the “SLI Type” button. Copy and paste the desired metric in the required field.
5. Complete the steps to create the SLO and click the “Save” button.

New Relic Examples​

1. Select an SLI type. a. If you choose “Availability”, select the following metric examples:Good metric: SELECT count(*)-sum(error) FROM TransactionValid metric: SELECT count(*) FROM Transactionb. If you choose “Latency”, select the following example:SELECT average(duration) FROM Spanc. If you choose “Throughput”, select the following example::SELECT count(*) FROM Transactiond. If you choose “Saturation”, select the following example:SELECT average(apm.service.cpu.usertime.utilization) FROM Metric WHERE appName LIKE '%'

If the query is valid and satisfies the requirements, you should see a green checkmark.

Example: Error using the “SINCE” keyword​

Query: SELECT average(apm.service.cpu.usertime.utilization) FROM Metric WHERE appName LIKE '%' SINCE 30 MINUTES

When you run the query, the Blameless Validation engine will throw the following error message:

Error: NRQL Syntax Error: Error at line 1 position 108, unexpected 'SINCE': error while querying metrics from New Relic

Example: Error using the “TIMESERIES” keyword​

Query: SELECT average(apm.service.cpu.usertime.utilization) FROM Metric WHERE appName LIKE '%' TIMESERIES

When you run the query, the Blameless Validation engine will throw the following error message because of the use of the “TIMESERIES” keyword:

Error: Please do not include TIMESERIES clause, we'll add it when querying data

Example: Error using more than on column​

Query: SELECT average(apm.service.cpu.usertime.utilization), average(apm.service.memory.physical) FROM Metric WHERE appName LIKE '%'

When you run the query, the Blameless Validation engine will throw the following error message because of the use more than one column value in the query:

apm.service.cpu.usertime.utilizationapm.service.memory.physicalThe result is:

Error: wrong New Relic query, expected 1 element