Show HN: Reduce Ops by Managing oncalls, tickets, incidents over Slack https://ift.tt/OcxjC0z

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 @scrum-master - 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 - Create Tickets, Automatic RCA , Updates to Stakeholder ,ie, all Incident-Related Information On Slack Channel based on company's workflows requirements Would love to get the community’s feedback. https://www.pagerly.io/ November 9, 2023 at 06:24PM

Komentar

Postingan populer dari blog ini

Show HN: Interactive exercises for GNU grep, sed and awk https://ift.tt/OxeFwah

Show HN: My Book Bulletproof TLS and PKI (Second Edition) Is Out https://ift.tt/5PZ9mxF