Paging on Autopilot, Stop Wondering Who is On-Call

📟 Paging on Autopilot, Stop Wondering Who is On-Call

Alerting solutions like PagerDuty and Opsgenie are an integral part of our customers workflow. We are making it even easier to page the right people whenever you are tackling an incident, without wondering who is on-call.

We are introducing a new Task inside of our Automated Genius Workflow where you can automatically page people, team, or escalation policy depending on the condition of an incident. Some example use cases are page Infrastructure whenever a postgres-db incident occurs or page IMOC for every incident.

• Works with any alerting solution such as PagerDuty and Opsgenie
• Removes cognitive overhead and burden of wondering who to page during an incident as its automated
• Easy to configure with drag and drop editor in seconds
• No more wondering or fumbling with who has access to PagerDuty or Opsgenie logins

In Action

🌝 New & Improved

• 🆕 New configurations for incident creation module on Web that can now mirror Slack
• 🆕 All incident titles are assigned incremental numbers (e.g. #771) to more easily identify especially when duplicate sounding titles, similar to Jira
• 🆕 Ability to require users to connect their Slack accounts at sign up with new setting in Slack integration, no need for /rootly connect
• 🆕 Genius Workflow output in Slack is refactored to be less chatty to put more emphases on the output instead
• 💅 Improved UI navigation to Integrations is more accessible
• 💅 Added option to assign myself in top of roles drop down on Slack instead of searching for your own name
• 💅 Updated welcome email template that better guides users to install Rootly and declare their first incident
• 💅 Genius Workflow output on timeline is much cleaner looking
• 💅 Better support rendering code snippets in incident timeline when pinned on Slack
• 🐛 Fixed issue where status page timestamps were duplicated
• 🐛 Fixed issue where sometimes Jira tickets were inconsistently created
• 🐛 Fixed issue where some users experienced slower updates in the Slack overview message