⚗️ Pulumi Provider for Rootly

Hot on the heels of our API and Terraform provider, we are excited to launch our Pulumi provider!

Support for Pulumi further helps Rootly build our lead for being the most developer friendly and Infrastructure as Code ready incident response platform.

Pulumi is a IaC platform that leverages existing programming languages such as TypeScript, JavaScript, Python, Go, .NET, Java, etc.

Engineering teams can now manage Rootly directly in code making distributed ownership of their service ownership even easier.

No more needing to click into the Web platform to manage configurations, example use cases:

• Manage teams and roles
• Manage severities, incident causes, types, etc.
• Import infrastructure such as services and functionalities

Learn More

Docs: https://docs.rootly.com/integrations/pulumi
Installation: https://www.npmjs.com/package/@rootly/pulumi

🌝 New & Improved

• 🆕 Guidance - reminder to update summary if one hasn't been set (configurable in Workflows)
• 🆕 Guidance - reminder to assign roles if none have been assigned (configurable in Workflows)
• 🆕 Send Slack message Workflow task now supports sending to users assigned to a specific role (e.g. Commander, Scribe)
• 🆕 All time and date selectors inside of the Web platform display the users timezone
• 🆕 Pinned images and screenshots from Slack now appear in Notion postmortem
• 🆕 Alerts and Pulse Workflow conditions can be triggered by specific webhook payloads
• 🆕 Grafana integration supports taking snapshots of specific graphs
• 💅 All new accounts on Rootly have additional default Workflows (based on best practices) such as auto-archive incidents, assign role / update summary reminders, and prompts for incident feedback
• 💅 Continued investment across monitoring and observability to further improve our reliability
• 💅 Shortcut integration supports linking to epics
• 🐛 Fixed issue where action items did not also appear on the incident timeline
• 🐛 Fixed issue where Notion failed to create a postmortem page under extremely rare race conditions

📜 Notion Integration

We are excited to partner together with our friends at Notion and be featured on their integration marketplace.

Customers can now enjoy automatically generated postmortems and incident timeline where they document work already, Notion.

With Rootly + Notion installed, customers can:

• Create incident timelines automatically in Notion without copy-pasting from Slack
• Automatically populate incident metadata (e.g. severity, resolution time, service impact, etc) for consistent data every time
• Depending on the type of incident, different postmortem templates are dynamically used
• Jira tickets are automatically linked, e.g. action items

Learn more

Read full release by Notion: https://www.notion.so/releases/2022-05-10

Find Rootly on Notion integration marketplace: https://www.notion.so/integrations/all

🌝 New & Improved

• 🆕 Quick access selector for incident variables in the postmortem editor
• 🆕 Launched on Product Hunt https://www.producthunt.com/posts/rootly 😸
• 🆕 Incident variables for {{ incident.started_by }}, {{ incident.mitigated_by }}, {{ incident.resolved_by }}, and {{ incident.cancelled_by }}
• 🆕 Incident variables for {{ incident.mitigation_message }} and {{ incident.resolution_message }}
• 🆕 Ability to view and export Rootly status page subscribers
• 💅 Redesigned https://rootly.com/integrations making it even easier to navigate and discover
• 💅 Redesigned sign up and sign in pages
• 💅 Removed unnecessary links back to Rootly inside of various Slack event messages to reduce noise
• 💅 No longer alert the user assigned a particular role if the user assigning the role is the same
• 💅 Cleaned up copy around editing links in Slack to be more intuitive
• 💅 Slack channels within the Rootly platform can be searched with or without a hashtag # channel-name
• 💅 Delightful thank you page whenever you sign up for a personalized demo
• 💅 Cleaned up how incident timeline toggles are displayed (e.g. only show starred events)
• 🐛 Fixed issue where Rootly postmortem editor was occasionally not saving

👪 SCIM (System for Cross-domain Identity Management)

SSO and SCIM goes together like peanut butter and jelly.

We are excited to introduce SCIM to continue solidifying Rootly as the most enterprise-ready incident management platform on the market.

SCIM ensures your user data is secure and automates the user identify lifecycle (e.g. automatic deprovisioning).

What can you do?

• Provisioning - onboard all your users onto Rootly at once
• Creation - automatically create users in Rootly when you create a new user in your identity provider (all are supported)
• Deactivate - automatically remove users in Rootly when you delete a user in your identity provider

Does it work with any identify provider?

Yes! We are using SCIM 2.0 standard and compatible with any identity provider (Okta, Azure AD, Google, etc.)

Existing customers can try it today by visiting our Documentation.

🌝 New & Improved

• 🆕 Edit timestamps directly from Slack with /incident timestamp (e.g. Starting, Detected, Acknowledged, Mitigated, Resolved, etc)
• 🆕 Creating an incident from alerts that Rootly ingests now allow you to update incident details first instead of automatically declaring it
• 🆕 Ability to customize alert payload with custom incident copy and incident variables when you page from PagerDuty / Opsgenie
• 🆕 Services and Functionalities now support importing from Opsgenie
• 💅 Multiple company email domains can be used in a single Rootly workspace
• 💅 Postmortem custom fields are now separated by Rootly generated and external generated (e.g. Confluence, Google Docs)
• 💅 Better support for organizations with multiple workspaces in how we handle cross-channel interactions
• 💅 Changes and modifications to timestamps now show up in the incident timeline
• 🐛 Fixed issue where pinning images to incident timeline from Slack occasionally did not work first try
• 🐛 Fixed issue where the order of events on incident timeline were incorrect
• 🐛 Fixed issue in Google Docs workflow task where selecting a drive folder did not populate

🌿 Custom Fields

The most configurable incident management platform just got even more flexible!

We are announcing the ability to define custom fields anywhere in Rootly to ensure unique incident data can be captured, even if they're customer specific.

Endless use cases

• Which customers have been impacted?
• How the incident was detected?
• Revenue impact?
• What geographies were impacted?
• Were the right responders part of the incident?
• etc...

Customizable for any use case

• Supports both Slack + Web platform and can be separately configured
• Determine where custom fields should be captured: incident creation, mitigation, resolution, or postmortem
• Pick between single select, multi-select, and free text custom field types (more coming soon!)
• Set the fields as either optional or required

Are Workflows supported?

Yes! Any custom field defined will show up as a new condition inside of Workflows. That means you can run Workflows based on custom field inputs (e.g. emailing a specific customer when they are impacted).

Existing customers can try it today by visiting Configuration > Custom Fields.

🌝 New & Improved

• 🆕 Trigger in Workflows for when roles (e.g. commander, scribe, etc) are assigned
• 🆕 Ability to update Rootly generated integration links via /incident integrations command (e.g. replace Zoom bridge with existing one)
• 🆕 See why our customers rated us ⭐⭐⭐⭐⭐ on G2!
• 🆕 Import PagerDuty services to Rootly functionalities
• 🆕 Incident updates (Mitigated, Resolved) in main incident announcement (#incident, #warroom) channel have the option to be threaded
• 💅 Owner has been renamed to Reporter to bring greater clarity who created the incident
• 💅 Incident variable {{ incident.subscribers | map :email }} to invite any participant in the incident to postmortem review meeting
• 💅 Running /incident help brings up all Rootly commands faster
• 💅 Better support for PagerDuty escalation policy when auto assigning roles
• 💅 Descriptions for roles support markup and links by default
• 🐛 Fixed issue where modifying incident timestamps weren't saving
• 🐛 Fixed issue where users without permission to invite teammates still saw the option (although it didn't work for them)

📆 Automatically Schedule Postmortem Reviews

Reviewing and learning about your incidents in a blameless way is critical to improving your incident management program.

We are making scheduling postmortem review meetings even easier via a new Workflow task.

• Supports Google Calendar
• Dynamically add attendees to the review meeting based on involvement with {{ incident.subscribers }}
• Add permanent attendees (e.g. Infrastructure manager)
• Set how long after the incident is resolved and duration of meeting

More importantly, build discipline and habits around coming together and sharing incident knowledge.

🌝 New & Improved

• 🆕 Integration links on Web platform are editable, e.g. you want to use an existing Zoom bridge and not the one Rootly generates
• 🆕 Confluence uses the latest version called "new editor"
• 🆕 Browsing available commands in /incident help now lets you directly execute them without retyping the slash commands
• 💅 Full sized image import in Google Doc postmortem timeline for any pinned item
• 💅 Ability to unsubscribe from transactional incident update emails
• 💅 New icon displayed next to major new features
• 💅 Easily access Rootly's blog and changelog at the bottom of every weekly summary email to stay up to date
• 💅 Incident Slack channel URLs are hyperlinked in timeline on Web platform to reduce visual clutter
• 💅 If users manually connect their Slack account via /incident connect, we now display a confirmation message to show it was successful
• 🐛 Fixed issue related to postmortem timeline formatting on Confluence
• 🐛 Fixed issue related to duplicate incidents being displayed on rare occasions

📟 Auto Create Incidents from Any Alert

We are launching the ability to automatically create incidents from any alert source via Workflows.

• Monitoring tools - Datadog, Grafana, Nobl9, etc.
• Paging and alerting tools - PagerDuty, Opsgenie, VictorOps, etc.
• Ticketing and tracking tools - Zendesk, Asana, etc.

Customers can configure a Workflow to ingest specific alerts from various external tooling and set a task to automatically kick-off incidents, regardless of source. This will spin up an incident channel on Slack, invite responders, start a Zoom, and/or whatever was configured.

Why did we build this? Because incidents can stem from many different sources such as programmatically, human detected, and more.

Rootly is the single aggregation point for all types of incidents and that can be created and managed consistently every time.

🌝 New & Improved

• 🆕 Design overhaul for timeline in Web platform to improve navigation and readability
• 🆕 Auto-assign Reporters and Assignee to Jira tickets in Workflows, e.g. {{ incident.creator.email }}
• 🆕 Automatically record to cloud or local for Zoom bridges created with Workflows
• 🆕 Conditions in Workflows for set and unset (e.g. run Workflow A if Service is blank)
• 💅 Ability to unsubscribe from status page updates
• 💅 Datadog snapshots and dashboards posted into the incident channel by Rootly link back to Datadog
• 💅 Running /incident list displays incident titles alongside their status
• 💅 UI improvements to https://rootly.com/blog

🧪 Terraform Provider for Rootly

We are excited to introduce our long- awaited Terraform provider making infrastructure as code effortless.

Engineering teams can now manage Rootly directly in code making distributed ownership of their service ownership even easier.

No more needing to click into the Web platform to manage configurations, example use cases:

• Manage teams and roles
• Manage severities, incident causes, types, etc.
• Import infrastructure such as services and functionalities

Our Terraform provider can be found here and documentation here.

In addition, we also have our Rootly API available, learn more here.

🌝 New & Improved

• 🆕 Ability to configure preheader text in send email task sent via Workflows
• 🆕 Ability to turn on/off broadcasting of incident updates in channel vs. just threaded message, found in Integration > Slack
• 🆕 Templates in Workflows can be accessed as a pop-up
• 💅 Updated Jira and Confluence scopes to leverage the latest versions
• 💅 Additional guidance to Bookmarks task and PagerDuty task in Workflows
• 💅 Reliability enhancements across how we handle backend Slack interactions
• 💅 Updated /incident help with /incident support and /incident convert command and guidance
• 💅 If roles are being reassigned we no longer notify the channel reducing noise
• 💅 Improved descriptions around Kind of incidents (e.g. Test / Training, Incidents, Scheduled Maintenance) in Workflow conditions
• 💅 Improved internal error reporting to more easily identify customer specific issues
• 🐛 Fixed issue where users could not unassign roles after the incident was resolved in Web
• 🐛 Fixed issue where active incident count on Web dashboard was incorrect
• 🐛 Fixed issue where some users occasionally were not being invited via PagerDuty
• 🐛 Fixed issue where searched items in Web occasionally did not send users to the right incident

🪂 Get Support From Rootly in Slack

We are making accessing Rootly support and engineering team even easier.

We are waving goodbye to support portals, Zendesk, and other methods.

Anyone from within Slack can run /incident support to file a ticket (report bug, get help, etc.) with Rootly. As always, you'll still have access to us via Slack Connect channels.

If urgent, we trust our customers to even page our engineering team and we'll wake up.

Why did we do this? This is part of our continued investment to ensure our customers have a successful implementation day 1 and day 365+. A few other helpful tools.

• /incident tutorial - guided and customized tutorials to teach your users, learn more.
• /incident test - create test incidents to get hands on experience with Rootly without false alarms
• /incident convert - channels you might forget to create with Rootly can be turned into Rootly incidents, learn more.

🌝 New & Improved

• 🆕 One-click re-integrate Slack to upgrade permissions without needing to uninstall first
• 🆕 Export action items to CSV
• 🆕 Bookmark automatically created whenever a new integration is configured
• 🆕 Support for preheader text in send email Workflow task
• 🆕 URL that automatically opens up incident creation on Web: https://rootly.com/account/incidents/new
• 💅 Ability to hide manual Workflows drop-down as part of incident creation wizard on Slack
• 💅 User prompts to upgrade Slack permissions to unlock new features
• 💅 Deleting all roles will hide role assignment on Slack
• 💅 Added Twitter links to Changelog page, keep up with our latest updates!
• 💅 Deleting and editing Services, Types, Functionalities, and other conditions now require two less clicks
• 🐛 Fixed issue where postmortems could not be bookmarked
• 🐛 Fixed issue where https://rootly.com/integrations/slack had confusing Add to Slack links

🔖 Bookmark Anything in Incident Slack Channel

We are introducing a new Workflow that allows you to bookmark any link, integration, or resource to the incident Slack channel.

Customers can now append the most critical information at the top of incident channels making it immediately accessible.

Built on top of our Workflows engine, not only are there powerful defaults out of the box but can be customized to suit any organization.

• Have different bookmarks for different types of incidents (e.g. Security playbook vs. Infrastructure playbook)
• Specify Title, Link, and Emoji
• Out of the box incident dashboard and relevant integrations are bookmarked

So, what can you bookmark automatically? Pretty much anything, here are a few examples.

• Integrations (e.g. Jira issues, Zoom rooms, Confluence postmortems, PagerDuty on-call schedule, etc.)
• Internal resources (e.g. Datadog dashboards, etc.)
• Playbooks / Runbooks (e.g. Restarting the database, Cloud provider outage, etc.)
• ...endless possibilities!

🌝 New & Improved

• 🆕 The Rootly team will be at SREcon San Francisco from March 14-16 at Booth 111, come say 👋
• 🆕 Condition in Workflows to specify Test / Training incidents that enable ability to build customized training
• 💅 Canceled incidents do not show up on Dashboard anymore
• 💅 Revamped /incident update modal
• 💅 Rootly.com is more mobile responsive and friendly
• 🐛 Fixed issue where Rootly status page updates were formatted incorrectly

🧞 Convert Existing Channels to Rootly Incidents

Rootly provides the most comprehensive suite of onboarding tools to help companies rapidly adopt better incident management.

As with the introduction of any tool, you won't always remember to use Rootly for new incidents due to muscle memory.

For the times you forget, we are introducing /incident convert that allows you to turn existing incident channels into Rootly incidents.

• Continue collaborating on incidents without losing context or stopping your conversation
• Incident history preserved and no need to manually backfill into Rootly
• Link to existing incidents if an on-going incident had already been created
• Prompts to fill in incident details as if you were just creating a new incident (e.g. Severity)
• Supports private incident channels

🌝 New & Improved

• 🆕 New coat on paint on Rootly.com with shiny new logos, testimonials, and product features
• 🆕 Reordering teams in Web reflect the order displayed in Slack create and update incident wizard
• 🆕 Ability to reorder components on Rootly status page
• 🆕 Ability to resend invites to Rootly with one click in Organization Members
• 🆕 New incident variable for {{ incident.roles }}
• 🆕 Integrations when incidents are created are shown as hyperlinks
• 💅 Increased number of times we refresh and check for new Slack channels, reminder you can always go to Integration > Slack > Refresh Channels without waiting
• 💅 Weekly summary emails are now sent Monday at noon instead of Friday end of day, enjoy your weekend!
• 💅 Playbooks are displayed in two columns instead of one to reduce visual clutter
• 💅 Continuing major refactoring internally to ensure Slack commands are even more resilient
• 💅 Removed /incident connect step in /incident tutorial as all new users are automatically prompted to connect
• 🐛 Fixed issue where removing labels from Jira did not save for some users
• 🐛 Fixed issue where selecting State in Linear Workflow task did not populate results for some users
• 🐛 Fixed issue where clicking save on Linear in Integration gave users an error page despite saving correctly
• 🐛 Fixed issue where postmortem download to PDF was stalling
• 🐛 Fixed issue where we displayed a duplicate Workflow task for inviting on-call users to Slack channels