onpage logo

What's Post-Mortem Reporting?

According to sources:

“Blameless post-mortems allow us to examine mistakes in a way that focuses on the situational aspects of a failure’s mechanism and the decision-making process of individuals proximate to the failure.” The DevOps Handbook

The engineers at Google define post-mortem reporting as, “[A] written record of an incident, its impact, the actions taken to mitigate or resolve it, the root cause(s), and the follow-up actions to prevent the incident from recurring.”

Post-Mortem Reporting

audit trail

Significance of Post-Mortem Reporting

Post-mortem reports provide insights into the cause of an incident. Teams can deconstruct a particular incident and see what transpired after the critical event to determine how it can be improved in the future.

Was the problem due to a scheduled or unscheduled incident? When the SEV-1 incident occurred, was the right team notified? If the team was notified, did they actually hear the alert or did the alert just go off as an indistinguishable, unprioritized ping on their smartphones?

 

OnPage's Real-Time and Post-Mortem Reporting

Real-Time Insights

The reporting dashboard provides quick, real-time views into all activities, including the number of messages received each day, top responders and methods used to respond to an incident. With these insights, managers can better estimate workloads and resources, view resolution progress and response times. They can also determine which team members are spending the most time responding to issues and reassign upcoming incidents to others to provide relief.

Post-Mortem Reporting

Real-Time Audit Trails

Teams gain instant visibility into incident notifications, escalations and acknowledgments via time-stamped audit trails. This report shows the subject of the alert message, when it was created, who responded and when they responded. Managers use real-time audit trails to ensure that incidents are being managed effectively by the right people at the right time.

Post-Mortem Reporting

Downloadable Reports

Post-incident reviews (PIRs) and post-mortem meetings are now easier to prepare with downloadable metrics reports. Teams can review the data, discuss and discover any issues. By examining the data, teams can take actionable steps to improve incident response performance.

Downloadable reports provide information on the number of alerts sent and the quantity of incidents that occurred. These reports also offer a record of time-stamped responses, missed notifications and the team members involved in responding to an incident.

Reports reveal whether the incident response workload is equally distributed across teams. Administrators can take steps to balance the workload to ensure that respondents are always motivated.

Post-Mortem Reporting

Video: OnPage Post-Mortem Reporting

Gain instant visibility into your team’s incident load by month and response performance through OnPage’s Reporting Dashboard. Watch the video to learn more. 

New Feature Enhancements

Sophisticated Dashboard Data

We are pleased to announce a refreshed UI to the OnPage dashboard. The new, modern interface incorporates enhancements that make interactions intuitive without compromising the efficacy of intelligence reporting. The advanced dashboard provides a detailed snapshot of responder activities and message statistics.

Message Notes on Report Console

The OnPage reporting console now allows users to compose incident notes. Transcribe what occurred during the incident and detail when critical events were resolved. OnPage message notes are fully downloadable and perfect for post-incident analysis.

 

Powerful Live Call Routing Reports

Gain intelligent insights into your team’s live call routing usage with time stamps and response statuses via OnPage’s Live Call Routing reporting dashboard. Managers can export these customizable reports for further incident analysis.

 

See OnPage in Action!

Learn more about Real-Time Reporting, Escalation Policies and On-Call Scheduling. Request a demo.

  • This field is for validation purposes and should be left unchanged.