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 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

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