The following steps are available:
Acknowledge or Close Incident: automatically acknowledge or close an existing incident in New Relic.
In the example above, the flow creates an alert and initiates an xMatters incident when a signal from New Relic comes into xMatters. When a user acknowledges the notification, the New Relic incident is updated, and when the incident's status to changed to Resolved in xMatters, the New Relic incident is closed.
To add a New Relic step to your flow:
- Go to the Apps tab of the palette, expand New Relic section, and drag the Acknowledge or Close Incident step onto the canvas.
- For instructions on using the New Relic trigger, see New Relic Incidents trigger.
- Connect the step to the previous step in the flow. This gives you access to the alert properties and outputs of previous steps when you configure this step's inputs.
- Double-click the step to edit it, and use the Setup tab to configure the inputs. You can use plain text and input variables (or both). See the following section for detailed information on the inputs, including which are required.
- On the Endpoint tab, configure the step to point to your New Relic instance.
- You can select a pre-existing endpoint or create a new endpoint.
Using the Acknowledge or Close Incident step does not resolve the incident in New Relic; you may continue to receive notifications until the incident is resolved.
Use the Acknowledge or Close Incident step to automatically acknowledge or close an existing incident in New Relic. Map outputs from previous steps to the inputs to complete the incident details.
Inputs with an asterisk* are required.
|New Relic user key to authenticate the request. This user is also recorded as acknowledging or closing the incident.|
|New Relic Incident ID*||ID of the New Relic incident to update.|
|Action*||The action to perform on the New Relic incident: Acknowledge or Close.|
This step has no outputs.
Flow Designer includes a built-in New Relic Incidents trigger that initiates a flow when it receives a signal from a New Relic webhook. You can configure the webhook to send the request when your configured conditions are met.
Add the trigger to the canvas
- Go to the Triggers tab in the palette, expand the App Triggers section, and drag the trigger onto the canvas.
- Double-click the trigger (or click the pencil icon).
- 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 to use as the authenticating user.
- Click the Flood Control tab to edit the trigger's default flood control settings. For more information about these settings, see Trigger Flood Control.
- Click Done.
- 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.
- In New Relic, go to Alerts and AI and select Notification channels from the drop-down menu.
- On the top right-hand side of the screen click New notification channel.
- 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 to notify when the alert fires to the end of the URL.
- For URL authentication, use an ampersand to attach recipients. 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.
- For other authentication types, use a question mark to attach recipients. For example, if you want to notify Barry Gull and the on-call members in the group responsible for the Cassiopeia service, you'd add ?recipients=bgull,cassiopeia to the URL.
- You must URL-encode any special characters or spaces in the target names.
- 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.
The trigger has the following outputs you can use as inputs to steps further along the flow.
|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 of the alert in New Relic. Valid values are:
|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.|