Overview
The reports page is a great way to get a high-level overview on how your users, teams, and overall company is performing in respect to incident response and resolution.
The reports page is broken up into 2 sections:
- User Reports - Reports that are specific to users
- Incident Reports - Reports that are specific incidents.
Each section has its own unique filters, that filter each section independently.
User Reports
Time On-Call (Burnout)
The Time On-Call report is especially useful to see how often someone has been on-call, or will be on-call. This report should be used as a signal if one user is on-call too much, and if others could help bear the load of on-call.
The target for this report should be to distribute on-call days equally.
Users MTTR
The users Mean Time To Response (MTTR) report is useful in identifying how fast (or slow) users are responding to incidents.
Incident Reports
Incidents Over Time
The incidents over time report is a great way to show a timeline of incident history. It can help identify when larger events happened (e.g. system outages or major deployments).
Incidents By Day
The incidents by day report is an easy way to identify which days most incidents occur on. You can use this report to retrospect events that happen on certain days (e.g. deployments) or forecast support.
Incidents By Source
The incident by source report is an easy way to identify which user or integration is creating most incidents.
Incidents MTTR
The incident Mean Time To Response (MTTR) report is useful in identifying how fast (or slow) incidents are being responded to.
Incidents By Status
The incident by status report gives an overview into the state of incidents as a whole. The desired result is the entire graph showing resolved.
Incidents By Urgency
The incident by urgency report gives an overview to the priority of incidents being created. Optimally you would want the following distribution of urgencies: low > medium > high > critical.
