Workflows Can Now Automatically Update Previously Posted Slack Messages

๐Ÿ’ฌ Workflows Can Now Automatically Update Previously Posted Slack Messages

With Rootlyโ€™s configurable workflows, the app can automatically post to Slack when you take certain actions like updating the incidentโ€™s severity or status. Weโ€™re adding another degree of control here by allowing you to choose whether you want workflows to post a new Slack message or update a previous one. Choosing to edit previously posted messages helps you eliminate confusion from out-of-date messages in your incident Slack channel.

You can change this setting by enabling the โ€œReplace Parent Messageโ€ option in workflows that post to Slack. With this option, Rootly will edit the previous message from the workflow instead of posting or threading a new message. When this happens, youโ€™ll see text below the Slack message that shows that the message was automatically updated by Rootly, and at what time the last update happened. This reduces clutter in the channel and ensures responders donโ€™t risk reading incorrect information from an outdated Slack message.

Hereโ€™s a quick video demo:


๐ŸŒ New & Improved

๐Ÿ†• Retrospective are no longer locked strictly for post resolutionโ€”now they can be created and accessed during any phase of the incident
๐Ÿ†• Assignees in Linear can now be automatically assigned via workflows
๐Ÿ’… Added the ability to auto-update incident when Jira ticket is updated
๐Ÿ’… Implemented guardrails to prevent non-stop loops on workflows
๐Ÿ› Fixed incorrect incident status and incident link display on Action Items metrics table
๐Ÿ› Addressed issue with cancellation messages not being logged in the incident timeline


Automate Component Status Updates on Statuspage.io

โฑ๏ธ Automate Component Status Updates on Statuspage.io

We've made an exciting upgrade to our Statuspage.io integration: customers using Statuspage.io can now use Rootly to automatically update component statuses. Prior to this upgrade, teams that wished to mark a specific component as operational, degraded_performance, partial_outage, major_outage, under_maintenance, or offline, would need to manually publish to their status page. This upgrade enables you to simply set up your workflow(s) once, and Rootly will automatically publish to the status page and place each component in the correct status.

How it Works:

  1. Connect your Statuspage.io account. Youโ€™ll simply need to link your statuspage.io account with your Rootly account once, and you're ready for configuration!
  2. Import an existing status page. Use an existing page from your Statuspage.io account instead of creating a net new in Rootly.
  3. Leverage the power of JSON and Liquid. The advanced setup section in the Publish Incident to Status Page task allows you to set the exact component(s) you want to update and the status(es) you want to set them to.
  4. Automated task using a workflow. Once a trigger event occurs, Rootly automatically detects the change and updates the component(s) status(es) on your Statuspage.io page. This means your page stays up to date without any manual intervention.
  5. Notify subscribers in real time. The workflow will also handle real-time notifications to keep stakeholders, customers, and internal teams informed on each status change.

Why it Matters:

  • Improved Incident Response SLA: By automating status updates from Statuspage.io, Rootly ensures that the right people are alerted at the right time, reducing your Mean Time To (MTTx) metrics.
  • Enhanced Transparency: Real-time system health updates foster transparency and trust with customers and stakeholders. Which in turn, enhances your reputation and overall customer experience.
  • Increased Efficiency: Eliminating manual status updates allows your team to focus on incident resolution, rather than administrative overhead.
  • Streamlined Communication: Consistent and accurate incident updates across all channels provides clarity during high-pressure situations.

Checkout this short video to see a sample use case and learn how to set it up:


๐ŸŒ New & Improved

๐Ÿ†• Added user_id as an optional request body parameter to the Create a Incident API to allow teams to programmatically create incidents on-behalf of another user
๐Ÿ’… Added Cancel button to escalation dialog on web UI to improve visual consistency across all platform dialogs
๐Ÿ’… Improved user experience by dynamically displaying subscription options on status pages based on the enabled subscription methods
๐Ÿ› Fixed spotty Slack command responses for multi-org accounts integrated to Slack Enterprise
๐Ÿ› Fixed incorrect private user display in Slack incident channels


Rootly Joins the Vendr+ Marketplace

๐Ÿ›’ Rootly Joins the Vendr+ Marketplace

Weโ€™re making it even easier to get started with Rootly by joining the Vendr+ software marketplace, an invite-only program available only to the top SaaS products. In addition to the AWS Marketplace, Vendr+ provides another quick, streamlined option to purchase Rootly as your incident management platform. Vendr+ is available to the hundreds of customers worldwide who use Vendr to handle their software procurement negotiations.

Learn more about the benefits of using Vendr+ here.

๐ŸŒ New & Improved

๐Ÿ†• Adding a Slack message to timeline via ๐Ÿ“Œ emoji can now be configured to only add the message to the incident timeline and not pin the message in the Slack channel.
๐Ÿ†• Added subscription method grouping to the subscribers page of each status page. Now admins can easily identify how someone is subscribed (e.g. via email or phone).
๐Ÿ’… Updated status page notification email to be more reader-friendly.
๐Ÿ’… Updated ghost text in Scheduled Maintenance status page dialog to be more specific to maintenances.
๐Ÿ› Fixed UI bug where Services field was not displaying on the web UI.
๐Ÿ› Corrected {{incident.previous_attributes.status}} value to store previous values, not current.


Assign Multiple Users to the Same Incident Role

๐Ÿ‘ฅ Assign Multiple Users to the Same Incident Role

By popular request, weโ€™ve shipped an update to allow you to assign multiple users to the same incident role!

As always, this setting is highly customizable so you can choose which roles allow for multiple users. For example, you may want to be able to have multiple data analysts indicated during an incident, but only allow for one incident commander.

You can configure this under Configuration > Incident Roles. When you add a new role or edit an existing one, youโ€™ll see an option to โ€œAllow Multiple Users To Be Assigned This Roleโ€. With this enabled, you can easily assign users to roles right in Slack.

Hereโ€™s a quick demo:


๐ŸŒ New & Improved

๐Ÿ†• Rootly status page subscription options are now configurable
๐Ÿ†• Added ability to define multiple HTTP status codes as success condition for HTTP Client workflow task
๐Ÿ’… Improved user experience by opening linked Slack channels directly in Slack, instead of opening in browser and then redirecting to Slack
๐Ÿ’… Backfill incidents are now supported in workflows
๐Ÿ› Fixed inability to clear previously set Severity field in Create Incident workflow task
๐Ÿ› Corrected In Triage At field to be an optional field on the Timestamps dialog on web UI


Incident Triage: Investigate Potential Incidents Faster

๐Ÿš‘ Incident Triage: Investigate Potential Incidents Faster

Start tracking potential incidents as soon as they develop, without the pressures of kicking off all the processes that come with declaring an incident. When you use the โ€œIn Triageโ€ feature, weโ€™ll create a triage incident while you investigate and get the right people in the room. From there, you can choose to update the incident status to โ€œstartedโ€ to declare an active incident, or โ€œcanceledโ€ to track how the problem was resolved and close it.

Some benefits of incorporating triage status into your incident management:

  • Capture incident data sooner
  • Avoid duplicate efforts due to lack of visibility
  • Reduce on-call fatigue from false alarms
  • Create a greater sense of psychological safety around starting incidents

To get started with triage incidents, head into Configuration settings from your main menu in the web platform and navigate to โ€œForms & Custom Fieldsโ€. Click โ€œConfigureโ€ for the form you want to add Triage to (this will typically be your โ€œNew incidentโ€ form to start out with), and add the โ€œMark as In Triageโ€ field. With this field added, youโ€™ll be able to create triage incidents in Slack or in the web platform just like any other incident, by simply toggling the โ€œIn Triageโ€ option in the form when the incident is created.

Triage also supports its own set of workflows, so you can determine exactly what you want to happen when a triage incident is started. When creating custom workflows, youโ€™ll find โ€œIn Triageโ€ in the status options.

Check out a quick video demo of triage in action below and learn more about the benefits of this feature in our latest blog post.


๐ŸŒ New & Improved

๐Ÿ†• Introduced Auto-Assign Role from On-Call Rotation and Invite On-Call to Slack Channel capabilities for VictorOps integration
๐Ÿ†• Custom boolean fields can now be created with independent Name and Description fields
๐Ÿ’… Enabled liquid variables containing URLs to be clickable links in retrospectives created in Google Doc
๐Ÿ’… Up-versioned Terraform to v1.0.7 with a lot of improvements and fixed. See our Changelog.
๐Ÿ› Fixed the Page VictorOps On-Call task to allow paging via escalation policy or user
๐Ÿ› Fixed broken link on Integrations page for Statuspage.io docs


Rootly + Fivetran Data Connector Integration

๐Ÿ”— Rootly + Fivetran Data Connector Integration

Incident data provides valuable insights into the health of your business. Rootly provides plenty of built-in, customizable metrics right in the web platform, but for organizations that want to dive even deeper into their data, we recommend using a data connector to pull your Rootly data right into your centralized data location.

The Fivetran Rootly connector is a fully managed data integration for delivering real-time, efficient data replication from Rootly to your destination of choice. The ELT connector extracts a deep level of data from the source, replicates and loads that data in your centralized data warehouse or data lake, represented in an easy-to-navigate schema, where your analysts can easily access and query it alongside the rest of your organization's critical information.

See this quick setup guide for instructions on how to set up this data connector.

๐ŸŒ New & Improved

๐Ÿ†• You can now use the Update a Google Doc task to update retrospective tasks and timelines in your own Google Doc templates
๐Ÿ†• Action items manually exported to Jira are now accessible directly from the Rootly web UI
๐Ÿ’… Optimized response time on Export to Ticketing feature for a better user experience
๐Ÿ’… Improved retrospective timelines by removing distracting events such as user joining a Slack channel
๐Ÿ’… Removed query text on snapshot graphs retrieved from New Relic for a cleaner display
๐Ÿ› Fixed issue with auto-adding two identical code snippets on the Send Slack Block task
๐Ÿ› Fixed issue with the Subject field not being able to be left empty on Update a Zendesk Ticket task


Less Noise, More Flexibility: New Slack Notification & Emoji Options

๐Ÿ™‰ Less Noise, More Flexibility: New Slack Notification & Emoji Options

We heard your feedback and made some adjustments to provide greater control and flexibility around how you configure Rootly in Slack. All of these can be easily adjusted in your Slack integration settings page. Hereโ€™s whatโ€™s new:

You can now disable user tagging on default threaded updates, like automatic timeline events. This can be adjusted by toggling โ€œMention user on timeline eventsโ€ on or off based on your preferences. This can reduce noise for incident responders, while still providing confirmation that automated actions have been completed successfully.

testing

Youโ€™re also no longer required to use the default emojis to perform actions in your Slack integrationโ€”you can now assign any emoji you want to pin events to the timeline, create a task, or mark as a follow-up action item. You can even assign multiple emojis to perform these actions!

Here's a quick demo of both of these customization options in action:


๐ŸŒ New & Improved

๐Ÿ†• Introduced the ability to perform user lookup in workflows using a userโ€™s name, email, or Slack ID
๐Ÿ†• Naming of the downloaded retrospective PDF can now be dynamically set by altering the retrospective title
๐Ÿ’… Manual Export to Jira feature can now dynamically display required fields based on Jira Project Key and Issue Type
๐Ÿ’… Incident duration displayed on retrospectives are now displayed with a more detailed time (H:M:S)
๐Ÿ› Fixed inability to open dashboard reports sent by workflows
๐Ÿ› Fixed inability to provision custom roles using SCIM groups in Okta


SCIM Group Support: Access Control Made Easy at Enterprise Scale

๐Ÿ”‘ SCIM Group Support: Access Control Made Easy at Enterprise Scale

We're thrilled to add SCIM group support to our growing suite of enterprise-friendly features. Whether you have a team of 10 or 10,000, you can onboard new Rootly users in your organization seamlessly by auto-assigning roles in Rootly based on their SCIM group membership, all from within any SCIM-compatible SSO platform (Okta, Azure AD, Google SSO, etc.). Want to ensure everyone in your customer support team can access Rootly as an observer? Or that every engineer has the ability to start an incident? Simply assign any of your SCIM groups a corresponding Rootly permission type.

Managing user permissions at a group levelโ€”typically corresponding to teams or business streamsโ€”is essential for businesses operating at enterprise scale, and SCIM (System for Cross-domain Identity Management) is the trusted standard for this secure access management. With SCIM group support, we're making it even easier for enterprises to onboard and manage their users simply and securely in one place.

Learn more about SCIM support in our help docs.


๐ŸŒ New & Improved

๐Ÿ†• Users will receive automated emails from Rootly when their third-party integration tokens are nearing expiry
๐Ÿ†• New {{incident.google_drive_parent_id}} liquid variable to reference the desired parent folder in Google drive for Google docs created automatically with Rootly workflows
๐Ÿ’… We've enhanced our integration with New Relic by allowing alerts to automatically create incidents in Rootly
๐Ÿ’… Updated incident titling logic to avoid duplicate incident titles
๐Ÿ› Fixed minor bug in Zendesk integration (fields can now be left empty when creating a new Zendesk ticket without reverting to the default placeholder text)


Integrate With External Systems via HTTP Client

๐Ÿ“ฒ Call External APIs from Rootly

We are thrilled to introduce a new addition to our ever-growing list of workflow tasks: the HTTP Client task! With this latest addition, organizations can now make outbound request calls to external APIs directly within their workflows.

Here are the key highlights of the HTTP Client task:

  • Seamless Integration via Workflows: The HTTP Client task seamlessly integrates into your workflows, enabling you to incorporate external API calls to your incident response automation. Whether you need to retrieve data or perform write actions, this task has you covered.
  • Versatile HTTP Methods: The new task supports a wide range of HTTP methods, including GET, POST, PUT, and more. Youโ€™re well-equipped to find the appropriate operation for the API you're interacting with.
  • Flexible Request Parameters: You can specify headers, query parameters, and request bodies to match the unique contract of each external API.
  • Heightened Security with Secrets: Rest assured that your API calls are secure and reliable. You can leverage Rootly Secrets to reference API keys, tokens, etc. to ensure that sensitive data is never exposed at any point in the call.

The new HTTP Client task opens up a whole new world of possibilities for integrating with external services and systems. Common enterprise use cases are all just a workflow task away!

  • Event logging can be supported by firing off an API call to an external audit service each time a workflow is run in Rootly.
  • Asynchronous run jobs can be triggered to write to a data warehouse every time an incident is created or updated.
  • Incidents can be redirected to other Rootly orgs by calling Rootly APIs with org-specific API keys

Checkout this instructional video on how to get started with setting up an HTTP Client task.

๐ŸŒ New & Improved

๐Ÿ†• Added Update Notion Page task to enable overwriting of an existing Notion page
๐Ÿ†• Introduced the ability to turn user mentions off on timeline events to reduce notification noise
๐Ÿ’… Enhanced Form Fields page for better displaying of fields with extended names
๐Ÿ’… Improved role assignment logic for requesting permission upgrades to ensure accuracy
๐Ÿ› Fixed datepicker display issue on web UI
๐Ÿ› Fixed inability to delete previously added action items in Send Slack Message task


Custom Google Doc Permissions

๐Ÿ” Custom Google Doc Permissions

We're thrilled to announce our latest feature: the ability to update Google Doc permissions via workflows. This will allow InfoSec teams to streamline user permission management in security incidents.

We understand the importance of efficient collaboration and information security. Now equipped with the ability to update Google Doc permissions using workflows, teams can automatically grant and revoke user access to Google Docs.

Let's take a closer look at the key enhancements in this update:

  • Streamlined Permissions Management: We simplified the process of managing and updating Google Doc permissions. You no longer have to navigate to Google Docs to grant or revoke access for users joining the incident. Access can now all be controlled via Slack or the web UI.
  • Enhanced Security with Real-Time Permission Updates: Security incidents require stricter access control. You donโ€™t want non-participating users to have access to private incident documents. The new feature enables you to automatically revoke access as soon as a user is no longer subscribed to the incident. This prevents unwanted lingering access and helps organizations demonstrate compliance with data protection regulations.
  • Improved Team Efficiency: InfoSec teams face significant time constraints due to the critical nature of their incidents. The ability to automatically provision Google Doc access saves valuable time and effort by eliminating the manual process of managing access rights. This automation allows the response team to focus on more critical tasks like mitigating security threats and implementing improved security measures.

InfoSec teams are responsible for safeguarding sensitive information and ensuring that only authorized individuals have access to critical resources. With this new feature, InfoSec teams can effectively manage access control for confidential incident documents. This reduces the risk of unauthorized access and helps maintain the confidentiality of sensitive information

Here's an instructional video to help you get started on automating Google Doc permissions.


๐ŸŒ New & Improved

๐Ÿ†• Introduced notification emails to alert customers on failed token refreshes
๐Ÿ’… Added text to clearly call out which Service or Schedule is displayed on the on-call schedule dialog in Slack
๐Ÿ’… Updated Loom videos in Rootly Docs
๐Ÿ› Fixed inability to display Slack dialog when /incident status command is triggered
๐Ÿ› Fixed inability to select a single checkbox in Slack notifications setting
๐Ÿ› Fixed action item export issue in to Asana integration



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