Imagine an assistant engineer that takes over all the redundant and time consuming operational tasks. Diplo addresses - š Critical RCCA (post mortem) reports in minutes ā Time to resolution for incidents š Manage runbooks š Internal knowledge search
Hello Product Hunt!
No one loves on-call yet have to go through it every rotation. Busy on-calls causing burnouts in common. We decided to build Diplo with pin pointed features just alleviate engineers of this on-call toil and optimize operational costs. We would love to hear your take.
I would like to describe a few key features that we started out with -
RCCA reports
RCCA (Root Cause Corrective Action) or post mortem or retrospective reports is a critical document that needs to be prepared for every high impact incident that captures a detailed incident description, key timelines for mitigation and root causing, five whys analysis, corrective actions, SLO metrics etc. This easily takes up several hours for engineers, often there are several of these that overflow outside of the on-call shift.
ā Diplo handles prepared RCCA reports within minutes freeing up dev time for engineers.
Incident Insights
Incidents are often combination of multiple features being used in unexpected ways that sends on-call team on a ride, with each time a different on-call team looking at the issue from scratch.
ā Diplo leverages past incidents' knowledge to resolve current one faster
Knowledge source
Operational tasks are often haywire among Jira, Confluence wikis, Google docs, Notion and more.
ā Diplo connects it all within slack
To try out Diplo as a slack bot, reach us at https://www.diplo.cc/contact. We would also love to hear more use-cases based on your experience.
