Postmortems - Learning from Failure in a Blameless Way

Continuously improve with each incident

Solutions for the Victors of Innovation

The point of Postmortems (or post-incident reviews, since dead bodies are not relevant here) is to learn as much as possible about what happened before, during, and after an incident. The result is everybody has the same shared knowledge. But don’t assign blame. Blame discourages people from sharing what really happened.

VictorOps, a tool for incident management, offers a feature for powerful postmortems, in which you can review a timeline of all activity related to an incident, add notes and observations, and share action steps to take in the future.

You’re in Good Company

Incident Management Geared for DevOps

Say goodbye to vague alerts, reactive ops, and siloed teams. We’re improving our response to problems in the name of innovation. VictorOps provides observability, collaboration, and real-time alerting, so you can build, deploy, and operate software fearlessly.


Streamline the incident management process in favor of rapid remediation to reduce the break fix cycle – and make on-call suck less.

Learn More »


Align teams, tools, and channels to support cross-functional collaboration. Ask questions and share knowledge for transparent solutions.

Learn More »


Apply observability from deployment through incident remediation. With robust inputs and data, you foresee issues before they happen.

Learn More »

Integrate All The Things


Easily configure VictorOps as an alert action, sending Splunk’s data insights as alerts directly into VictorOps. Via Splunk Tokens, you’ll append dynamic, valuable alert information to rapidly send responders what they need.


See the full VictorOps incident payload, and acknowledge and resolve incidents right from Slack. The VictorOps functionality is mirrored in both systems and all activity is captured, so you have a complete black box of what happened.


Bidirectional communication between JIRA and VictorOps means your new issues, updates, and other workflow triggers in JIRA can flow to VictorOps, and changes to those incidents in VictorOps can flow back to JIRA as updates to the originating issue.


Connect Jenkins to ensure the right people have eyes on deployments in case of a problem. You’ll choose the specific build or deployment you wish to send to the VictorOps timeline, and receive notifications and any other contextual information.


VictorOps is broadly compatible with different versions of Nagios, enabling you to use custom code for local and remote service checks, notifications, and event handlers. We made sure that the VictorOps portal view is consistent with the view you see within Nagios.

New Relic

New Relic integrates with VictorOps so you can see end-to-end platform health and performance, as applications are running, in real time. Install this integration to send application performance alerts into the VictorOps timeline for full awareness and better collaboration.