Branded Emails and Custom SMTP Server

πŸ“₯ Branded Emails and Custom SMTP Server

As much as we love sending emails branded with Rootly (e.g. no-reply@rootly.com), we think making it your own helps communication be even clearer.

We are excited to launch the ability to integrate with your own SMTP server (e.g. alias@company.com) and have all emails come from your own domain.

We understand when communicating externally that having the brand Rootly might confuse your stakeholders. You can brand your emails with your own custom logo.

  • Customize subject line and preheader text with support for incident variables
  • Specify CC and BCC addresses
  • Option to send as many individualized and branded emails depending on use case (e.g. internal leadership, customer, etc)
  • Support for workflow tasks, triggered based on conditions automatically or manual
  • Customize body of email with incident variables

Existing customer can first setup their SMTP server inside integrations then configure in Workflows > Tasks > Send Email.

Note, this is optional. By default Rootly will send all emails on your behalf if nothing is configured.


🌝 New & Improved

  • πŸ†• Custom field for Textarea that offers adjustable text area, previously limited to single line for free form text
  • πŸ†• API for listing workflow runs
  • πŸ†• Added data sources for both Terraform and Pulumi provider
  • πŸ†• Our Rootly status page has migrated to a new Atlassian Statuspage
  • πŸ’… Update Incident workflow task includes the ability to update incident severity
  • πŸ’… Default metric filters for last 100 days and YTD out of the box
  • πŸ’… Clearer guidance for setting up Atlassian Statuspage integration
  • πŸ’… Polished UI for workflow tasks list for easier navigation
  • πŸ› Fixed issue where custom metrics dashboard URL was not redirecting correctly when shared
  • πŸ› Fixed issue where integrating with Confluence and searching for a space key did not work

Incident Variable Explorer

β›΅ Incident Variable Explorer

Since our launch of incident variables (see changelog), they have quickly become an integral part of Rootly.

Customers leverage it today to build workflows, better automate communication, deep customization (e.g. rename incident title to Jira ticket number), and more. However, with 100s of options, knowing which ones to use and if they work can be confusing.

We are excited to launch our Incident Variable Explorer that makes as the name suggests browsing, exploring, and testing incident variables even easier.

  • Browse incident variable output on a per incident basis
  • Interactive incident variable preview to test and see example outputs based on incident selected
  • View all available incident variable options with context instead of scrolling through generic docs
  • Preview incident variable data for not only incidents but postmortems, action items, alerts, and pulses
  • View incident variable data for all integrations (e.g. {{ incident.jira_issue_url }})


🌝 New & Improved

  • πŸ†• API endpoint for executing specific workflows
  • πŸ†• Partial matching support for sources, labels, and payloads inside of workflows alerts and pulses
  • πŸ†• Ability to define a name attribute in API key for easier identification
  • πŸ†• Ability to sync Rootly incident title and events with PagerDuty incident title and status updates
  • πŸ’… Alert when /incident workflow example-command is ran outside of the automatically created incident channel
  • πŸ’… Additional education resources now live on Backstage Community repo
  • πŸ’… Ability to update custom fields in Update Incident workflow task
  • πŸ’… Freshly updated docs around our Statuspage.io integration
  • πŸ’… Additional incident variables for Google Meet
  • πŸ› Fixed issue where incident cause was not being attached to postmortems for some users
  • πŸ› Fixed issue where renaming workflow groups for alerts reset the incident kind
  • πŸ› Fixed issue where editing the incident channel Slack URL did not save
  • πŸ› Fixed issue where where filtering with JSON for events caused some webhook events to improperly filter

Statuspage.io Integration - Component & Template Support

πŸ“‘ Statuspage.io Integration - Component & Template Support

We are excited to launch our Atlassian Statuspage.io integration with support for components and templates.

Customers will be able to manage all communication updates to Statuspage without needing to leave Slack or fumble around with logins and access.

Fast and transparent communication is crucial for successfully managing incidents. Update Statuspage using /incident statuspage or inside of the Rootly Web Platform.

  • Import Statuspage templates and apply them to any Rootly incident for consistent messaging and speed
  • Publish to multiple Statuspages (e.g. customer facing and internal facing)
  • Separately control what is displayed externally on Statuspage vs. the status of your Rootly incident
  • Individually select impact of Statuspage components (e.g. degraded performance, major outage, etc.)
  • Published updates are automatically shared in the incident Slack channel and incident timeline for visibility

Customers may choose to programatically update their Statuspage by leveraging workflows (e.g. if greater than SEV1 then publish Investigating update to Statuspage).

Getting started: https://docs.rootly.com/integrations/statuspage-io


🌝 New & Improved

  • πŸ†• Ability to convert public incidents to private
  • πŸ†• Create incidents option from Alerts view in Web Platfrom now allow modifying incident details before creation
  • πŸ’… Severity descriptions are shown when running /incident update
  • πŸ’… All workflows by default have Slack Command trigger to reduce confusion for manually ran workflows
  • πŸ› Fixed issue where /incident feedback was not working for some users
  • πŸ› Fixed issue where assigning roles in /incident test was not working

Sandbox Environments

πŸ–οΈ Sandbox Environments

We are making testing your configurations, workflows, and integrations safer and easier with sandbox environments!

A standalone instance of Rootly connected to a separate non-production Slack environment.

An important consideration was ensuring you can seamlessly switch back and forth between production and sandbox environments that does not require logging in and out. You can do this with our organization switcher (top right drop down).

To get started, let your Partnerships Manager know and we'll provision one for you!


🌝 New & Improved

  • πŸ†• Action items are shown on Notion generated postmortems
  • πŸ†• Scheduled start and end times added to incident timeline page
  • πŸ†• Attribute for private incident visibility in Rootly API
  • πŸ’… Ability to click move to reorganize workflows instead of drag and drop
  • πŸ’… Action items are linked on postmortem tab for easier reference
  • πŸ› Fixed issue where workflow for Jira subtasks were not being triggered
  • πŸ› Fixed issue where disabling the automatic creation of incident channels was not respected
  • πŸ› Fixed issue where roles were not showing up for /incident test
  • πŸ› Fixed issue where some users were getting invalid triggers error on duplicate workflows

Rollbar Integration

🍫 Rollbar Integration

We are excited to announce our Rollbar integration, one of the world's most popular error tracking and notification software.

For many of our customers, Rollbar is often detects errors related to incidents before anything else.

Now with the Rollbar and Rootly integration, customers can respond and gain context into incidents even faster, all-in-one place.

  • Ingest alerts created by Rollbar into Rootly (Web or Slack) with all relevant metadata
  • Triage Rollbar alerts in Rootly and create an incident with human in the loop
  • Automatically create incidents in Rootly is Rollbar alerts exceed a defined threshold

Getting started guide: https://docs.rootly.com/integrations/rollbar


🌝 New & Improved

  • πŸ†• Users can manage notifications in Rootly for email and Slack (User > Account Details > Notifications)
  • πŸ†• Workflow condition for contains alongside already existing ones such as is one of and is set
  • πŸ†• Workflow task for getting alerts
  • πŸ’… Rootly internal status page is now rebranded to Incident Timeline Page across all platforms
  • πŸ’… Colours in metrics automatically randomize colours if two are the same
  • πŸ’… Shiny new customer logos on https://rootly.com/, welcome aboard πŸ‘‹
  • πŸ› Fixed issue where help links in /incident help were broken

Beautiful Incident Timeline Pages

πŸ“£ Beautiful Incident Timeline Pages

We are excited to release beautiful incident timeline pages that can be easily shared across the organization.

Why? Following along incidents can be noisy especially given the amount of collaboration required to debug the issue. Teams such as customer support are left wondering what is applicable to them and often causes confusion leading to more questions.

Incident timeline pages solve that by providing a high level overview of everything that is important that teams can easily follow along.

  • Updates to the incident timeline page are pinned automatically with πŸ“Œ emoji in Slack
  • Updates to timeline in the Web Platform automatically updates the incident timeline page
  • Link can be easily shared across the organization to Rootly users
  • Executive overview of all relevant information without scrolling around in Slack
  • Accessible links in both the incident channel overview in Slack and incident view on the Web Platform


🌝 New & Improved

  • πŸ†• Send Slack Message and Slack Blocks task in workflows now can be sent as ephemeral (Only you can view)
  • πŸ†• Adding responders via Opsgenie and VictorOps now split into users and teams instead of combined for easier search
  • πŸ†• Custom field support for Asana integration
  • πŸ†• Ability to configure assignee for Asana integration
  • πŸ†• Stepped line chart support in metrics
  • πŸ†• Stacked charts support in metrics
  • πŸ†• API support for CRUD custom dashboards in metrics
  • πŸ’… Reworked data model for Statuspage.io integration that will unlock ability to leverage templates and components
  • πŸ’… PagerDuty integration better respects escalation policies and acknowledge events that is aligned with native PagerDuty
  • πŸ’… Infrastructure improvements to better support concurrent incident creation for a single organization
  • πŸ’… Action items in Web Platform grouped by their respective role, playbook, or other if applicable for easier categorization
  • πŸ’… PagerDuty and Opsgenie alerts are automatically closed when an incident is resolved
  • πŸ› Fixed issue where exporting metrics from specific charts as CSV and JSON did not work
  • πŸ› Fixed issue where elapsed time on Web Platform was not updating without a refresh
  • πŸ› Fixed issue in workflows if you set repeat every to 0 it causes an error

Manage Workflows via API, Terraform, and Pulumi

🧿 Manage Workflows via API, Terraform, & Pulumi

Rootly is the only enterprise-ready incident management platform that supports IaC via API, Terraform, and Pulumi.

Today, we are taking that one level further and enabling customers to manage workflows via API, Terraform, and Pulumi.

Workflows are at the heart of what makes Rootly able to be customized to encode each organizations individual incident processes.

Previously, managing these workflows (e.g. automatically create Jira ticket for on security board, invite infra team if SEV0, etc.) had to be done in our Web platform. This was manual and didn't align with how organizations were already leveraging IaC.

With the ability to now manage workflows through providers like Terraform, individual departments and teams can own workflow configuration without click-ops.

API

  • Docs with workflows support: here
  • Previous changelog release notes: here

Terraform

  • Docs with workflows support: here
  • Previous changelog release notes: here

Pulumi

  • Docs with workflows support: here
  • Previous changelog release notes: here


🌝 New & Improved

  • πŸ†• Scheduled maintenance can be created from Slack using /incident maintenance, previously only available on Web platform
  • πŸ†• Assigning action items to others easier in Slack by right clicking and selecting πŸ‘‰ assign a user/team
  • πŸ’… Improvements to make tasks associated with playbooks more robust
  • πŸ’… General refactoring on our data model and configurations that improves overall loading and saving speeds
  • πŸ’… Adding action items on Web platform no longer require a refresh to populate
  • πŸ› Fixed issue where filters on alerts were not working for environments and services
  • πŸ› Fixed issue where export to CSV and JSON did not specify the title of the custom field
  • πŸ› Fixed issue where updating the organization page rendered a 500 despite data always being saved

Customizable Incident Metrics

πŸ“Š Customizable Incident Metrics

We are excited to launch the industries most powerful reliability and incident insights.

Previously, customers relied on a basic set of metrics that weren't editable. Now, customers can build beautiful custom dashboards and charts with data sliced the way they want. Think BI tools such as Tableau and Amplitude. Example use cases now enabled...

  • Postmortems that haven't been published and exceed SLA
  • High severity incidents with action items
  • Custom field for customer impact
  • Incidents with a Jira ticket and type was customer facing
  • ...endless possibilities in our simple to use query and chart builder

Custom Dashboards

For a variety of reasons such as by engineering team, executive reporting, or type of insights, a single dashboard is not enough to serve all use cases.

  • Create private dashboards only you can view (can be upgraded to public)
  • Create public dashboards shared with the organization and team
  • Drag and resize various charts on dashboard for a custom look and feel

Charts, Filters & Queries

  • Build custom charts with multiple filter groups for granular reporting
  • Leverage filters not only for incident metadata like severity but also integration attributes (e.g. Jira tickets, Datadog playbooks, Confluence pages)
  • Use custom fields (e.g. customer impact) as an attribute
  • Select from a variety of chart types (line, chart, bar, table, aggregate value, etc.)
  • Custom label chart title and axis

Reporting & Exports

Making data driven decisions around reliability and where to invest resources have never been easier. Customers can now present to stakeholders various views depending on the audience type and focus.

  • Executive summary (e.g. top line metrics and trends)
  • Beautiful reports with full-screen presentation mode
  • Audience specific reports

Keeping the garden walls low in Rootly is key priority as many will want to export incident data to existing BI or analytics tools. Export options include.

  • API, CSV, JSON
  • PNG, JPG
  • PDF

Out of The Box

Although advanced and customizable, metrics out of the box are ready-to-go to get started quickly. Key data around MTTX, incident count, severity, service impact, and more fetched automatically. All wrapped in a beautiful UX. Teams of all sizes can take advantage of this!

GA for all customers on Rootly Enterprise to try! πŸ₯³


🌝 New & Improved

  • πŸ†• Workflow task for Update Rootly Postmortem
  • πŸ†• API fields include Slack channels, aliases, and owners for services, functionalities, and teams
  • πŸ†• Workflow condition for any on top of all of, any of, and none of existing options
  • πŸ’… Better deduplication when importing PagerDuty teams to Rootly
  • πŸ’… Shiny new logos on https://rootly.com/
  • πŸ› Fixed issue where guidance when assigned a role wasn't formatted correctly

Microsoft Teams Integration

πŸ“Ή Microsoft Teams Integration

We are excited to announce our video conferencing integration with Microsoft Teams.

As we further our market leading position for enterprise readiness, organizations will now be able to collaborate over Teams for high bandwidth conversations as they tackle incidents.

  • Create a Teams bridge automatically whenever an incident starts
  • Automatically bookmark Teams bridge to incident channel for easy access
  • Edit/replace Teams bridge link (e.g. if an existing one is already in use)
  • Leverage workflows to dynamically create Teams bridge (e.g. only SEV0 and SEV1 require a call)

Our Teams integration sits alongside other video conferencing tools already supported such as Zoom, Google Meet, Slack Huddles, Webex, and more.

Docs for getting started: https://docs.rootly.com/integrations/microsoft-teams


🌝 New & Improved

  • πŸ†• Specify notification channel whenever a workflow fails to run, found in Profile > Organization Settings
  • πŸ†• Service dependencies inside of Rootly service catalog
  • πŸ†• Alerts (e.g. PagerDuty) that Rootly pipes into Slack can now be customized with specific messaging and CTA buttons (e.g. create incident, link to alert, etc.), found in Workflow > Alerts
  • πŸ†• Workflow triggers for custom fields (e.g. custom field updated, etc.)
  • πŸ†• Action items can be exported to PDF
  • πŸ†• Incident timestamps (acknowledged, detected, started, mitigated, resolved) can be used as a workflow condition (set or unset)
  • πŸ’… Paging responders in Slack modal now separates escalation policies and users instead of combining
  • πŸ’… UI polishes around workflows and tasks
  • πŸ’… Infrastructure enhancements that makes bulk emailing and inviting users to Rootly better
  • πŸ’… Migration from PagerDuty webhook v2 to v3, enables additional event types around signal changes to incident severity, responders, and all around better sync between the two
  • πŸ’… Alerts tab added to main navigation menu in Web platform and Pulses is now nested under configuration
  • πŸ› Fixed issue where some users were prompted to reintegrate PagerDuty
  • πŸ› Fixed issue where workflow conditions for action items could run into a race condition
  • πŸ› Fixed issue where elapsed time in Slack did not update
  • πŸ› Fixed issue where clicking on an related active incident in Web platform did not redirect you to active incident channel

Microsoft Azure Active Directory SSO Integration

πŸ”‘ Microsoft Azure AD (Active Directory) SSO Integration

We are excited to be featured in the official Microsoft Azure AD application marketplace!

The vast majority of our customers leverage SSO and Rootly already, the most popular being Okta, Google, and Azure AD.

With continued support for Azure AD, enterprises can securely manage access to Rootly seamlessly.

  • Control in Azure AD who has access to Rootly
  • Enable your users to be automatically signed-in to Rootly with their Azure AD accounts
  • Manage your accounts in one central location - the Azure portal
  • Take advantage of SCIM

Getting started with Rootly and Azure AD, written by Microsoft: https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/rootly-tutorial


🌝 New & Improved

  • πŸ†• Shiny G2 badges for High Performer and Easiest To Do Business With for Summer 2022 on homepage πŸ₯³
  • πŸ†• Workflow task for updating an already created Google Calendar event (e.g. add more attendees programmatically to postmortem review meetings)
  • πŸ’… Google Calendar workflow task allows for modifying guest permissions (e.g. visibility of event, ability to invite others, ability to modify event)
  • πŸ’… Improved filter loading speed on Web platform
  • πŸ’… Improved filter UI with tasteful colours for easier navigation
  • πŸ’… More granular time settings for Google Calendar task (e.g. timezone support, wait time for skipping weekends)
  • πŸ’… Incident timeline loads 50 items instead of 10
  • πŸ’… 14-day free trial more accessible on homepage
  • πŸ› Fixed issue where emails after signing up for a trial were too noisy
  • πŸ› Fixed issue where there was a typo under incident type configuration
  • πŸ› Fixed issue where there was an UI bug for marking incidents as test on Web platform looked required


Rootly helps you respond to incidents faster as a team and learn to prevent them in the future.
wave