Product upvotes vs the next 3

Waiting for data. Loading

Product comments vs the next 3

Waiting for data. Loading

Product upvote speed vs the next 3

Waiting for data. Loading

Product upvotes and comments

Waiting for data. Loading

Product vs the next 3

Loading

Pagerly

Manage rotations, oncalls, incidents & ops over Slack

Pagerly is your Slack-based engineering sidekick ✔ Sync oncall schedules with Slack user group,overrides & reminders (PD, Opsgenie) ✔ Jira-Slack Sync ✔ Customized Incident Bot for channel, timelines & RCA ✔ Trusted by 100+ orgs like Dydx, Blockdeamon, Spotify

Top comment

Hello, Product Hunt! We're thrilled to be here! ✨ 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. Some of our common Engineering workflows are: - Sync your Pagerduty/Opsgenie/Github schedule with Slack UserGroup like @dev-on-call to manage threads easily - Round Robin rotations on Slack for non-oncall work say @scrum-master - Mention multiple oncalls together i.e @frontend-oncall mentions @android, @ios-oncall - Jira-Slack 2 way sync to create and manage tickets on Slack - Automatic Oncall Handover Reports -> Know your Incident trends, MTTR, Incoming Count - AWS IAM Access Requests over Slack - Give automatic cloud access to Oncall for debugging issue - Managing Time-based access for Engineer over Slack - Assign Tasks in Round Robin over Slack - A customised incident bot for your Organisation. We believe there is no single workflow that can work for all companies, hence we are open for building custom incident response bots . Some of the common workflows include: - Create Tickets / Incidents / Bugs within Slack - Create a Slack Channel Automatically Add All Stakeholders - Generate Timelines from Slack and Zoom messages - Create Action Items within Slack - Send Updates to Stakeholders within Slack - All Incident-Related Information On Slack Channel We are trusted by 1200+ teams including Spotify, BlockDaemon, MessageGears, Dydx, ITV, Mindtickle and much more!