New Relic Incidents

The built-in New Relic Incidents trigger initiates flows when it receives a request from a webhook in New Relic.

Add the trigger to the canvas

  1. Go to the Triggers tab in the palette, expand the App Triggers section, and drag the trigger onto the canvas.
  2. Double-click the trigger (or click the pencil icon).
  3. Set the authenticating user, and then copy the URL — you'll use this to set up the webhook in New Relic. Alternatively, you can create an integration user and use it as the authenticating user.

  4. Click the Flood Control tab to edit the trigger's default flood control settings. For more information about these settings, see Trigger Flood Control.
  5. Click Done.
  6. On the flow canvas, connect the steps you want to run when xMatters receives a request to that URL.

You're now ready to configure New Relic to target the trigger.

Configure New Relic to send requests to the trigger URL

To have New Relic send alerts to the flow trigger, you need to configure a webhook and set it to use the trigger URL.

  1. In New Relic, go to Alerts and AI and select Notification channels from the drop-down menu.

  2. On the top right-hand side of the screen click New notification channel.

  3. On the Channel details tab, fill in the following fields:
    • Select a channel type: Expand the drop-down menu and select xMatters from the list of available options.
    • Channel name: Enter a unique channel name.
    • Integration URL: Paste the URL from the trigger. Add the target names of any recipients you want xMatters to notify when the alert fires.
      • For example, if you want to notify Emma Pearson and the on-call members in the group responsible for the Antares service, you'd add ?recipients=epearson,antares to the URL. You must URL-encode any special characters or spaces in the target names.

  4. Click Create channel.

You're ready to use the webhook to trigger automated flows, including steps such as sending alerts and initiating incidents, though we always recommend testing before putting things into use.

Outputs

The trigger has the following outputs you can use as inputs to steps further along the flow.

Label

 Description

Recipients

 List of targeted recipients. Recipients are set by adding a recipients query parameter to the trigger URL when you configure the webhook in New Relic. See the instructions for configuring the webhook for details.
Current State

Current state of the alert in New Relic. Valid values are: 

  • open

  • acknowledged

  • closed
Signal Mode Determines the path the flow will take, based on the value of Current State parameter.
Signal ID Key or identifier used to terminate or correlate signals.
Incident URL Direct link to the New Relic controller.
Account Name Name of the New Relic account.
Condition Name Name of the condition that triggered the alert policy in New Relic.
Details Event message as defined in New Relic.
Duration How long the event has remained open.
Event Type Event type in New Relic.
Policy Name Name of the alert policy that triggered the alert.
Policy URL Direct link to the policy that triggered the alert.
Severity Severity of the alert in New Relic.
Timestamp Timestamp for the most recent alert in New Relic in epoch format.
Violation URL Direct link to the specific New Relic violation.
Raw Request JSON representation of the request. You can parse the raw request if you need additional details beyond the standard outputs.