Pager fatigue: Making the invisible work visible. Register now

Fallback expressions

July 1, 2025

If you’ve got a lot of alerting rules set up from different services across your organization, they won’t all have the same metadata or labels attached to them, which can make extracting “which team is responsible for this?” or “which service does this relate to?” tricky.

For example, some alerts might include a team=payments label directly, but others might instead have service=banking. With fallback expressions you can now consistently assign a team to these alerts no matter what they look like. For example:

  1. If there is a team attribute on the metadata of the payload, use that to notify a team
  2. Otherwise, if there is a service on the payload, use that to point to a service, then navigate to the owning team via Catalog

Coralogix alert source

We now have a new native alert source to support Coralogix. So, if you’d like to trigger incidents and escalations from a Coralogix alert, you can do so!

What else we’ve shipped

New

  • Workflows triggered by status page updates can run conditionally on whether subscribers are being notified or not

Improvements

  • We’ve refreshed and polished up the Security page in Settings
  • When adding a rich text alert attribute, we've clarified what formatting is supported
  • We improved the way we handle long URLs across various Slack surfaces
  • Improved performance loading follow-up statistics
  • The escalate Slack modal now informs you if nobody will be paged

Bug fixes

  • The list of alert attributes in the alert source configuration wizard is now scrollable
  • We fixed an issue where upon saving an alert source, the page would flicker with an error
  • We'll show a Terraform label for all your escalation paths that are managed in Terraform in "My escalation paths" section
  • In the escalations list, all expired escalations will now correctly show "Expired" as the latest action, rather than "Cancelled"
  • We'll no longer show you the option to re-order Catalog entries for types that are managed by incident.io, as the rank is never adjustable from Catalog
  • Organizations are now able to set up rules for merged incidents (i.e. to add a tag to incident tickets when an incident moves to "merged”)
  • Requesting access to a private incident without a channel now sends a message to the incident lead

So good, you’ll break things on purpose

Ready for modern incident management? Book a call with one of our experts today.

Signup image

We’d love to talk to you about

  • All-in-one incident management
  • Our unmatched speed of deployment
  • Why we’re loved by users and easily adopted
  • How we work for the whole organization