📟 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
🌝 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
- 🆕 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
We 💛 Google Docs
Many of our customers currently use Google Docs to write their postmortems. They enjoy the tooling for it's superior collaboration, ease of use, and familiarity as usually their entire company runs on it. However, when it comes to writing postmortems, although they prefer Google Docs, it's largely a manual process.
We are introducing our integration with Google Docs to automatically generate your postmortem after the incident is resolved. By enabling your Google Docs integration, Rootly will:
- Create a Google Doc under you desired Drive folder
- Populate the doc with a postmortem template as defined inside of Rootly (e.g. 5 whys)
- Populate incident metadata (e.g. incident title, severity, services impacted, resolution time, etc.)
- Generate incident timeline, no more copy-pasting from Slack!
- Disable native Rootly Dashboard postmortem experience and instead point users to Google Docs
🌝 New & Improved
- 🆕 Added a brand new Resources tab on the Rootly website. Everything from the hottest SRE jobs to our incident management blog!
- 🆕 Added a Genius Workflow task for auto archiving incident Slack channels
- 🆕 Export your incidents as a CSV
- 🆕 Added copy to clipboard option for postmortem timeline and incident data
- 🆕 After incident is resolved, users are prompted to edit their postmortem more explicitly
- 💅 Improved load times on Rootly Dashboard
- 💅 Improved reliability of PagerDuty integration that includes multiple redundancies
- 💅 Zoom, Google Meet, and other video conferencing options are globally turned on/off instead of per incident
- 🐛 Fixed issue where you could not unassign a user from an incident role in Slack
- 🐛 Fixed typos in
/rootly tutorialguide and in the Rootly Dashboard
- 🐛 Fixed bug where
/rootly tutorialwould not work for Slack users who had not linked their Rootly accounts yet
- 🐛 Fixed duplicate tags for key:value pairs that would occasionally pop up
Hi 👋 - welcome to our first Changelog where we will share exciting Rootly product updates on a regular basis. Stay up-to-date by subscribing to our newsletter below!
💌 Sharing Rootly with your Team
Whether you're a team of 20 or 20,000, we want to make it even easier to introduce / onboard your organization to Rootly based on a few guiding principles:
- Reduce work needed to teach others of a new tool
- Accelerate adoption via self-service
- Customizable towards your organization
We are introducing a new Slack command
/rootly tutorial that as the name states is a guided and interactive tutorial of Rootly.
- Comprehensive - takes all users from account setup, creating incidents, and finding help
- Accessible - command can be ran anywhere regardless if you have a Rootly account
- Beautiful - thoughtfully designed to be delightful to use and interact with
- Customizable - anywhere you want to provide additional context, we can link back to your internal docs on Confluence, Google Docs, etc.
🌝 New & Improved
- 🆕 This Changelog you are reading, thank you!
- 🆕 Support for additional incident milestones such as MTTA and MTTD.
- 🆕 Export incidents and metrics as CSV
- 🆕 Incident milestones (MTTA/D/M/R) and timeline in postmortems will reflect your local timezone
- 🆕 Supporting the ability to run Genius Workflows on a delay (e.g remind Slack channel to update postmortem 2 days incident is resolved)
- 💅 We migrated our documentation to docs.rootly.io hosted by Archbee (YC S21) to make it easier to find what you need
- 💅 You can decide what incident updates you want to broadcast to your global #incidents #war-room channels
- 💅 Can multi-select incident conditions such as incident type, services, environments, etc.
- 🐛 Fixed issue where the timer on Genius Workflows were slightly inaccurate
- 🐛 Fixed issue where pinning Slack messages that contained a hyperlink didn't show up
- 🐛 De-duplicate showing the same participant in incidents if the same user was assigned to multiple roles