PagerDuty Insights

Scrapes data about resolved incidents using the PagerDuty API and sends them to New Relic Insights. Runs on Azure Functions.

Setup instructions

1. Create/gather the API keys listed below.
2. Click the button above.
3. Pick a name and location for your function app.

Required application settings

• PAGERDUTY_API_KEY: Your PagerDuty API key (v2).
• INSIGHTS_INSERT_KEY: Your New Relic Insights insert key.
• INSIGHTS_ACCOUNT: The numeric ID of your New Relic account.

Interesting NRQL queries

Here are some sample NRQL queries you can run or use to build dashboards:

Who received the most alerts this week?

SELECT count(*) FROM PagerDutyIncident facet firstAssignedToName since 1 week ago timeseries auto

SELECT count (*) as 'Alerts received' from PagerDutyIncident since 1 week ago facet firstAssignedToName

What time of day are incidents occurring?

SELECT histogram(createdHour - 6, 24, 24) from PagerDutyIncident SINCE 1 week ago

Are incidents resolving themselves before anyone even acknowledges them?

This could indicate false or non-actionable alerts.

SELECT count(*) as 'Incidents' from PagerDutyIncident where acknowledgedBy is null and resolvedByType NOT LIKE '%user%' since 1 week ago

Have any alerts been slept through and escalated to the secondary on-call?

SELECT count(*) as 'Escalations' from PagerDutyIncident where escalations > 0 since 1 week ago

Credits

This project was inspired by a similar script authored by the New Relic team. Check it out for more NRQL queries and ideas.