Search Results

Start for free

Analytics - Exporting your data

Sometimes, your team needs to go even deeper with the data. For those times, you can export a broader range of data from our Data Export tab. We've included the same querying parameters and data as the chart pages with the addition of more summary exports.

Unlike our chart export, these CSV files will be sent directly to your inbox when they've finished processing. From there, the retrieval link will be valid for seven days. As long as you download it within that time frame, you're all set to use these files as you please, whether for custom analysis in a Jupyter notebook or as input data into a more comprehensive BI tool.

Quick Start

Let's get started! In this section, we will review the basic setup and navigation of the Analytics functionality.

  1. Select a report. Choose from various summary reports or chart data exports from the drop-down menu.

  2. Select a date range and filters. Using the Date Range picker, type in a start and end date using the MM/DD/YYYY format or select the range from the calendar interface by clicking on the calendar icon in the field. The date range currently defaults to UTC timestamps. For example, if you select a date range of 03/20/2022 - 03/23/2022, we will pull data between 03/20/2022 00:00:00 and 03/23/2022 23:59:59.

    1. Conditional filters can be used to refine the specificity of your query. You can apply none or multiple filters to a single query. We support the following filters:
      • Current severity
      • Current priority
      • Current milestone
      • Incident impacted infrastructure
      • Incident assigned teams
      • Incident attached Runbooks
      • Incident tags

  3. Generate a Preview. See the first 20 rows of your export to confirm that you're pulling the needed data before sending it to your inbox.

  4. Export CSV. Once you've confirmed your data, you can export the CSV. Once the file is ready, you'll be notified via email and provided a direct link to your file, valid for seven days. If there were any errors in running your report, you would be notified with a toast message or email, depending on what went wrong.

Note: By default, all GAMEDAY and MAINTENANCE severity incidents are omitted from the Analytics calculations.

There are numerous reports to select from. We can group them into two main categories: Summary Reports and Chart Data Export.

Summary Reports pivot on incident metadata, aggregating incident KPIs based on impacted service, functionality, severity, and more. The Chart Data Exports (denoted with a "-Export" in the title) are CSV downloads of the same information available in the previous tabs' charts. For more information on those reports, we suggest you look at the Chart Explanations.

If you’re still looking for more, take a look at the Raw Data Export integration here.

Detailed Data Export Explanations

Service Summary

How are all of your services performing? Key indicators, such as incident count and mean time metrics, give your business insight into your organization's service performance and can be a meaningful report for technical and product leads.

Data Dictionary

Column Name Measurement Unit Value Type Description
Name n/a string Service name as entered into service catalog by the user
Start Date YYYY-MM-DD hh:mm:ss UTC datetime Start date selected as query parameter
End Date YYYY-MM-DD hh:mm:ss UTC datetime End date selected as query parameter
Number of Incidents Incident count int Count of new incidents created for the service during the specified date range
Total Incident Duration ms int Total duration of incident measured with incident start timestamp and resolved milestone timestamp; this will be blank if no incidents have been created during the date range
MTTD ms int Mean time to Detected metric for incidents created during the specified date range; calculated with incident start timestamp and detected milestone timestamp
MTTA ms int Mean time to Acknowledged metric for incidents created during the specified date range; calculated with incident start timestamp and acknowledged milestone timestamp
MTTM ms int Mean time to Mitigated metric for incidents created during the specified date range; calculated with incident start timestamp and mitigated milestone timestamp
MTTR ms int Mean time to Resolved metric for incidents created during the specified date range; calculated with incident start timestamp and resolved milestone timestamp

Functionality Summary

How are all of your functionalities performing? Key indicators, such as incident count and mean time metrics, give your business insight into your organization's functionalities performance and can be a meaningful report for technical and product leads.

Data Dictionary

Column Name Measurement Unit Value Type Description
Name n/a string Functionality name as entered into service catalog by the user
Start Date YYYY-MM-DD hh:mm:ss UTC datetime Start date selected as query parameter
End Date YYYY-MM-DD hh:mm:ss UTC datetime End date selected as query parameter
Number of Incidents Incident count int Count of new incidents created for the functionality during the specified date range
Total Incident Duration ms int Total duration of incident measured with incident start timestamp and resolved milestone timestamp; this will be blank if no incidents have been created during the date range
MTTD ms int Mean time to Detected metric for incidents created during the specified date range; calculated with incident start timestamp and detected milestone timestamp
MTTA ms int Mean time to Acknowledged metric for incidents created during the specified date range; calculated with incident start timestamp and acknowledged milestone timestamp
MTTM ms int Mean time to Mitigated metric for incidents created during the specified date range; calculated with incident start timestamp and mitigated milestone timestamp
MTTR ms int Mean time to Resolved metric for incidents created during the specified date range; calculated with incident start timestamp and resolved milestone timestamp

Responder Summary

Who is spending their time in incidents? Key indicators, such as incident count and duration, give your business insight into who is jumping into incidents to help manage individual burnout and identify potential single points of failure in our people.

Data Dictionary

Column Name Measurement Unit Value Type Description
Responder Name n/a string Name of the Responder (Users) in your organization; not currently limited to a Role
Start Date YYYY-MM-DD hh:mm:ss UTC datetime Start date selected as query parameter
End Date YYYY-MM-DD hh:mm:ss UTC datetime End date selected as query parameter
Number of Incidents Incident count int Count of new incidents created for the service during the specified date range
Total Incident Duration ms int Total duration of incident measured with incident start timestamp and resolved milestone timestamp; this will be blank if the Responder had not been assigned to any incidents created during the date range

Severity Summary

How do your operations vary based on Incident Severity? Key indicators, such as incident count and mean time metrics, give your business insight into your organization's incident response processes.

Data Dictionary

Column Name Measurement Unit Value Type Description
Name n/a string Severity name as entered into Severities set up by the user
Start Date YYYY-MM-DD hh:mm:ss UTC datetime start date selected as query parameter
End Date YYYY-MM-DD hh:mm:ss UTC datetime End date selected as query parameter
Number of Incidents Incident count int Count of new incidents created with the given Severity during the specified date range
Total Incident Duration ms int Total duration of incident measured with incident start timestamp and resolved milestone timestamp; this will be blank if no incidents with specified severity were created during the date range
MTTD ms int Mean time to Detected metric for incidents created during the specified date range; calculated with incident start timestamp and detected milestone timestamp
MTTA ms int Mean time to Acknowledged metric for incidents created during the specified date range; calculated with incident start timestamp and acknowledged milestone timestamp
MTTM ms int Mean time to Mitigated metric for incidents created during the specified date range; calculated with incident start timestamp and mitigated milestone timestamp
MTTR ms int Mean time to Resolved metric for incidents created during the specified date range; calculated with incident start timestamp and resolved milestone timestamp

Incident Summary

What is your overall incident performance? Key indicators, such as incident count and mean time metrics, give your business insight into your organization’s health and can be a meaningful report for technical and product leads.

Data Dictionary

Column Name Measurement Unit Value Type Description
Start Date YYYY-MM-DD hh:mm:ss UTC datetime start date selected as query parameter
End Date YYYY-MM-DD hh:mm:ss UTC datetime End date selected as query parameter
Number of Open Incidents Incident count int Count of incidents that were in milestones detected through mitigated during the selected date range
Number of Resolved Incidents Incident count int Count of incidents that moved into the resolved milestone status during the selected date range
MTTD ms int Mean time to Detected metric for incidents created during the specified date range; calculated with incident start timestamp and detected milestone timestamp
MTTA ms int Mean time to Acknowledged metric for incidents created during the specified date range; calculated with incident start timestamp and acknowledged milestone timestamp
MTTM ms int Mean time to Mitigated metric for incidents created during the specified date range; calculated with incident start timestamp and mitigated milestone timestamp
MTTR ms int Mean time to Resolved metric for incidents created during the specified date range; calculated with incident start timestamp and resolved milestone timestamp

Last updated on 3/28/2023