New Relic Integration Guide

Pointers

• The integration is between a TaskCall service and New Relic.
• Incidents will automatically resolve in TaskCall when metrics fall back within the normal threshold.
• Incidents will be acknowledged in TaskCall when they are acknowledged in New Relic.
• This integration only allows alerts to be received in TaskCall from New Relic.

In TaskCall

1. Go to Configurations > Integrations and click New Integration.
2. Select the New Relic integration.
3. Give the integration a name and configure how incidents will be created. Only the Default Service field is required. The rest are optional.
4. Incidents (Optional)
   1. TaskCall automatically maps incoming payloads with internal attributes to create incidents. However, this can be customized in the Incidents tab. Constant values can be included alongside placeholders to dictate which attributes should map to the Incident Title, Description, Tags, Snapshots and Vendor URL. To insert a placeholder use double curly braces.
      
      
      
      For example, if you enter {{ alert.title }} in the Incident Title field, TaskCall will look for an attribute called "title" nested inside another attribute called "alert" in the incoming payload. If the nested attribute exists, its corresponding value will be pulled from the payload and inserted. If the nested attribute does not resolve successfully, TaskCall will fall back to the default mapping.
      
      If you are unsure, please leave the fields empty. TaskCall will use the default mapping to create the incident for you.
   2. Select the Urgency level the incident should be created at.
   3. Select the option to Group similar alerts together if you would like follow up triggers from the same alert source to be grouped into the same incident. If you leave this option unchecked, then a new incident will be created for every trigger. (This behavior is specific to new triggers; not updates to an alert.)
   4. Click Next to move on to the Services tab.
5. Services (Required)
   1. Select the Default Service incidents should be sent to. To route incidents to different services instead, set Map With Attribute to the attribute to route by using a placeholder. Then, map each value it can take to the service that should receive it.
      
      For example, to route by a region attribute sent in the payload, set Map With Attribute to {{ region }}, then map US to one service and EU to another, and so on.
      
      
   2. Click Next to move on to the Authorization tab.
6. Authorization (Optional)
   1. The Authorization tab allows a Bearer Token and an IP Allowlist be added if you would like to restrict who is able to send alerts to this integration. If you are unsure, this can be skipped.
7. Once done, click Save.
8. Copy the Integration Url that is issued for the integration. This will be used to set up the notification in New Relic.

In New Relic

In New Relic you will need to create a new destination and a workflow to ensure alerts are dispatched to TaskCall when certain policies are met.

1. Go to Alerts > Destinations. Add a new Webhook destination.
2. Give the webhook a name and paste the integration url you copied over from TaskCall in the Endpoint URL field. No authorization is needed. Click Save Destination when you are done.
   
   
   
   
3. Now go to Alerts > Workflows. Add a new workflow.
4. Give the workflow a name. Select the policies for which this workflow should apply and the priority with which they will be sent. In the Notify section, select Webhook. This will open up another modal where you can define the notification destination and message.
   
   
   
   
5. In the notification modal, select the TaskCall destination you created earlier as the Destination for this notification. You can leave the body of the message to be the default template set by New Relic. If you want to customize it, please refer to the attributes TaskCall expects. When you are done, send a test notification to ensure the integration is working correctly. Click Save message when you are done.
   
   
   
   
6. Click Activate workflow when you are done. That's it!

Alert Payload

TaskCall expects the following payload from New Relic. If a different payload is sent, TaskCall will still try to create an incident with it with the available data.

Customize Incident Body

By default, TaskCall shows the JSON payload received from New Relic as the body of the incident. However, it can be customized by passing a details attribute in the payload. The details attribute can be a single value or it can be a key/value pair. The value will always be converted into a string upon receipt in TaskCall. Here is an example of how the details attribute can be used: