New Relic

6min
Purpose
Echoes can connect to your New Relic account and monitor your incidents lifecycle in order to produce some metrics such as the Mean time to recovery﻿.
Installation
New Relic integration is done through the integrations settings. The installation will guide you into generating a User API key. 
Make sure to select the appropriate region.
New Relic connection
﻿
Once the connection is made you will be invited to select the New Relic Account on which to install Echoes
New Relic account selection 
﻿
Echoes will then install a Destination (Webhook) on the selected New Relic account.
Setting up your New Relic Workflow
The next step is to setup a New Relic Workflow in order to send incidents' events to Echoes through the Destination previously set during the installation.
The destination to be selected is Echoes webhook 
New Relic Workflow configuration
﻿
Requirements on the message template
The only requirement expected from Echoes is that the message template includes the issueId i.e
JSON
{
    "id": {{ json issueId }}
}
{
    "id": {{ json issueId }}
}
﻿
Reference an Echoes team as owner of a Service
A service may represent an application, a component, to open incidents against.
In order to associate a Service suffering an incident to a team in Echoes, the property serviceOwnerTeamId is to be set in the notification payload.
JSON
{
    "id": {{ json issueId }},
    "serviceOwnerTeamId": "cbdf76fc-3015-4c66-a5f8-143a48734e48"
}
{
    "id": {{ json issueId }},
    "serviceOwnerTeamId": "cbdf76fc-3015-4c66-a5f8-143a48734e48"
}
﻿
The team ID value itself could be held by a specific tag. When setting up the New Relic Workflow this tag could then be referenced in the template to be loaded dynamically when constructing the notification payload.
How to get the correct team ID from Echoes?
The team IDs can be found by using our Teams API.
Updated 26 Apr 2023
Did this page help you?
PagerDuty
Datadog