Show HN: Reduce Ops by Managing oncalls, tickets, incidents over Slack
Hi HN! In all the organisations, we have worked, SDEs and EMs spend a lot of time on on-call, incident operations, ticket operations - Constantly updating everyone on the current status of an incident, figuring out who is the current Oncall in Slack threads like @dev-oncall, Missing following up on Action Items post-incident, creating a post-mortem RCA document, Spending time on creating and analysing oncall reports For each of these tasks, there is a Developer who doesn't like to spend time on these tasks and an Engineering leader who stresses maintaining this culture. This is why we started Pagerly. : We believe Slack is the best place for collaboration, and many of these tasks can be done there effectively given the right workflows. Ex - Sync your Pagerduty/Opsgenie schedule with Slack UserGroup like @dev-on-call - Round Robin rotations on Slack for non-oncall work say @scru
Why it failed
Hi HN! In all the organisations, we have worked, SDEs and EMs spend a lot of time on on-call, incident operations, ticket operations - Constantly updating everyone on the current status of an incident, figuring out who is the current Oncall in Slack threads like @dev-oncall, Miss
- Kind
- startup
- Status
- Shut down
- Inventor
- gaurav_goel
- Ended
- 2023
- Source
- hackernews