In all the organisations, we have worked and talked to, engineers and leaders spend a lot of time on on-call and incident operations, in addition to debugging the issue itself.
Constantly updating everyone on the current status of an incident
Tired of figuring out who is the current Oncall in Slack threads like @dev-oncall
Missing following up on Action Items post-incident
Immediately creating a post-mortem RCA document
Spending time and creating oncall reports during handovers
For each of these tasks, there is a Developer who doesn't like to spend time and an Engineering lead who is stressing on maintaining this culture. We also know there are a lot of ad hoc tasks that come up as part of daily work.
We believe Slack is the best place for collaboration and a lot of these tasks can be done on Slack effectively given the right workflows.
This is what we’re solving for you at Pagerly
With Pagerly, you can
- Sync your Pagerduty/Opsgenie schedule with Slack UserGroup like @dev-on-call
- Create Round Robin rotations on Slack for non-oncall issues say @scrum-master / @writer-of-month , etc
- Mention multiple oncalls together i.e @frontend-oncall mentions @android, @ios ocnall - Jira-Slack 2 way sync to create and manage tickets on Slack
- Automatic Oncall Handover Reports -> Know trends, MTTR, fragile service
- A customised incident bot for your own company
- Create Incidents / Tickets/ Bugs from Slack
- All Incident Related Information On Slack Channel
- Automatic RCA
- Send Status Updates to your stakeholders
We have grown to 1000+ teams and would love to get the community’s feedback.
No comments yet.