Reporting: Using our API to create custom reports

Follow

Our customers have created all kinds of reports using our REST API to drill down on metrics and data that are important to them. Here are some examples: 

Graphite – This Ruby integration script collects PagerDuty incident metrics and sends them to Graphite, an open-source, scalable realtime graphing system. Users can collect numeric time-series data, send it to Graphite, and create monitors and charts to help your team visualize outage specifics. (Note: This is using v1 of our API). 

Opsweekly – Etsy created this handy, multi-purpose tool with the premise that on-call time should be quantified. It generates a weekly report and lets on-call engineers track their notifications to assess the signal-to-noise ratio of the alerting system. Over time, your team can gather enough data to get in depth reports like, for example, what alerts wake people up the most, the average alert volume per day, and on-call improvements over the last year. Engineers can also integrate their Opsweekly to their Fitbits or Jawbone UPs to provide insight into how being on-call is affecting them. It tracks lost sleep time and Mean Time to get back to Sleep (MTTS), and provides data that could help teams determine what alerts really call for disrupting an engineer’s REM. (Note: This is using v1 of our API). 

Zoho Reports – You can use Zoho Reports to query our API and build dashboards from the data. We recently published a post about how to import PagerDuty data into Zoho Reports and run SQL queries against it to build out your reporting features and track which services and escalation policies had unusually high (or low) incident volumes and Mean Time to Repair (MTTR). (Note: This is using v1 of our API). 

Incident details and body – This python script exports all incident details for a specific incident or range of incidents and includes the incident body. (Note: This is using v1 of our API). 

pager-hours – This script exports on-call hours for all users on all schedules within a PagerDuty account. (Note: This is using v1 of our API). 

pagerduty-alert-volume – A quick command-line to get the incident volume assigned to an escalation policy broken down by week. (Note: This is using v1 of our API). 

incident notes – This script exports incidents and their notes into a CSV file. (Note: This is using v1 of our API). 

Pigeonhole – Pigeonhole takes data from PagerDuty and generates graphs based on this data over a configurable time period. (Note: This is using v1 of our API). 

Have more questions? Submit a request

Comments