Overview
New Relic sends alerts through a Webhook destination, rendering a Handlebars template over the issue payload. A Workflow decides which issues are sent and on which transitions.Prerequisites
- Permission to create destinations and workflows in New Relic.
- A service created in aciona.me and linked to a team with an active schedule.
1. Create the alert source in aciona.me
Under Alert sources, create a source of type New Relic. Copy the URL and the token.2. Create the Webhook destination
Under Alerts → Destinations → Webhook → Create:1
Name
aciona-me2
URL
https://ingress.aciona.me/webhooks/<alertSourceId>3
Secure custom header
Name
X-Aciona-Token, value <sourceToken>. New Relic masks the value after saving.4
Payload template
Paste the recommended Handlebars template:
3. Create the Workflow
Under Alerts → Workflows → New workflow:1
Filter (optional)
For example, only issues with
CRITICAL or HIGH priority.2
Notify → Add destination → Webhook
Select
aciona-me.3
Notify when — the critical step
Open the “Notify when” menu and make sure BOTH are checked:
- ✅
Activated - ✅
Closed
4. Test
Use Test workflow to send a sample payload. Confirm the incident under Incidents. To validate auto-resolution, wait for an issue to close naturally (or close it manually) and confirm the matching incident was resolved.How fields are translated
State
The decision follows this order of precedence:triggerEvent = INCIDENT_CLOSED does not resolve the incident. In New Relic’s Issues model, an issue can hold several sub-events; closing one of them does not mean the issue is over. Resolving there would close the incident too early.Severity
Service
The hint comes, in order, from the affected-service tag, the entity name, the condition name and the policy name. Tag your entities with a service tag that matches the name in aciona.me.Troubleshooting
The incident opens but never closes
The incident opens but never closes
Closed is not checked under “Notify when” in the Workflow. Check it and test again.Webhooks suddenly stopped arriving
Webhooks suddenly stopped arriving
New Relic puts destinations into automatic snooze after consecutive errors (4xx, 5xx or timeouts). Check the destination status in New Relic. To catch this proactively, create an NRQL alert on
NrIntegrationError with category='NotificationError'.Title shows as Untitled alert
Title shows as Untitled alert
The template does not emit
issueTitle. Use the recommended template.Severity lower than expected
Severity lower than expected
New Relic’s historical template maps
HIGH to WARNING in a legacy field. Emit priority explicitly, as in the template above — it takes precedence.