Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the New Relic connector page.How webhooks are set up
StackOne creates and manages the webhook subscription automatically when the account is connected, and removes it when the account is disconnected. There is nothing to configure in New Relic and no URL to paste.
Review what StackOne creates in New Relic
On connection, StackOne adds three items to the New Relic account named on the connection. You can see them in New Relic under Alerts, but do not edit or delete them while the connection is active.
- A webhook destination named StackOne Events that points at StackOne.
- A webhook channel that sends each alert issue update as JSON.
- A workflow named StackOne Events that forwards every alert issue in the account on all notification triggers.
Enable the events you need
Enable the New Relic events you want in StackOne. The workflow already covers every notification trigger, and StackOne dispatches only the events you have enabled.
Available webhook events
The events below can be enabled for this connection. They follow the lifecycle of New Relic alert issues. Only events selected in StackOne are delivered, and each one carries the issue id in issueId and the underlying change in triggerEvent.
Review alert issue events
Events related to alert issues opened by New Relic alert policies and conditions.
- Issue Activated (
issue.activated) — Fired when an alert issue opens. - Issue Acknowledged (
issue.acknowledged) — Fired when a user acknowledges an alert issue. - Issue Priority Changed (
issue.priority_changed) — Fired when an alert issue’s priority changes, for example when a critical incident joins it. - Issue Closed (
issue.closed) — Fired when an alert issue closes, either because its incidents resolved or because a user closed it. - Issue Updated (
issue.updated) — Fired for any other issue update, such as a new incident being added or the issue being marked as investigating.
Delivery format
Details of how New Relic delivers events to StackOne.
Review the delivery format
New Relic sends one request per alert issue notification, and each request describes a single issue. One change can fire more than one notification. When a critical incident joins an open issue, for example, New Relic sends a priority-changed notification and an incident-added update about a second apart. New Relic Test notifications carry fixed sample data, and StackOne acknowledges them without dispatching an event.