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.
Datadog integration is done through the integrations settings. The installation will guide you into generating an organization’s API key and an Application key.
For the Application Key we encourage to create a Service Account as key holder.
Make sure to select the appropriate site.
Once the connection is made you will be invited to select the Datadog Organization on which to install Echoes
Echoes will then install a webhook integration on the selected Datadog organization.
It is advised to create a custom role specific to Echoes and associate the role to the user the Application Key has been issued for.
The following permissions are required for Echoes to interact with Datadog:
- Integration Manage
- Service Catalog Read
Setting up your Datadog incident notification rule
The next step is to setup an incident notification rule in order to send incidents' events to Echoes through the webhook previously set during the installation.
The destination to be selected is Echoes_webhook
Configure the events to be sent if State is to change or Echoes TeamID (Optional).
Reference an Echoes team as owner of a Service (Optional)
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 Echoes TeamID is to be added to the incident's property fields as a custom field. This field is not mandatory.
It is to be defined as a Text Area and a User Input
The team ID value itself can then be set via the incident attributes on the incident page
How to get the correct team ID from Echoes?
The team IDs can be found by using our Teams API.