Alert Filtering, Tags in Alert Webhooks, End Linked Zoom Meetings, and more

Alert Filtering

Alerts in the user interface can now be filtered according to various facets such as impacted Service, Functionality, or Environment, Teams, matched Rule, and more!

This makes it much easier to trace how Alerts make it into your system and which components they align with.

Other Fixes and Improvements

• 💅 Tags can now be included in the Signals alert webhook body, and they can be used to tag related Services, Environments, and Functionalities. Find more information in our Events Data model here
• 💅 We have added a new Runbook step for End Linked Zoom Meetings. For all Zoom meetings linked to the incident, you can proactively automate terminating them so that recordings can be processed immediately
• 💅 We have added Liquid previews and snippets for custom values when configuring Jira field mapping
• 💅 When someone on your team claims a shift coverage request, we now post into the team Slack channel or DM the coverage requester in Slack if a team Slack channel doesn't exist
• 💅 We've added connection health checks for Opsgenie integration. You should now see a "Connection health" section in your Opsgenie settings
• 🐛 Fixed an overflow issue where the conditions dropdown in Runbooks was cut off in the modal
• 🐛 Fixed an issue where Signals was counting against the number of integrations in accounts
• 🐛 Fixed an issue in Runbooks where field validation was triggering after clicking away from any field. We now trigger field validation when users try to click "Add Step" and there are required fields not filled out
• 🐛 Fixed an issue where Create or Rename Slack incident channel Runbook step could not be saved due to empty Communications field
• 🐛 Fixed a bug where multi-select fields in the FireHydrant UI were not validating correctly