Flexible filtering in Insights

When filtering on the incidents page, you've always been able to choose between Matches all and Matches any. That second mode is now available in Insights too, so you can express conditions across fields in a single view. For example:

• "All incidents in scope for the major incident report" — Severity is one of [Critical, Major] OR Has external status page = Yes
• "All incidents for this field, before and after a migration" — Impacted product = Payments OR Affected features contains Payments, e.g. where older incidents carry the old value on one field and newer ones the new value on another.

This is available across all our new built-in Insights dashboards, with custom dashboards to follow shortly.

In addition to that, there’s far more filtering options available for incidents: you can now filter on all the properties supported on the incident list page, such as:

• If a timestamp is set
• If an incident has follow-ups or a post-mortem
• If the incident has a public statuspage

Post-incident flow dashboard glow up

The Post-incident flow dashboard in Insights has had a refresh, now with near real-time data and new ways to slice it. Use it to understand how incidents move through your post-incident flow — what proportion complete, opt out, or get stuck — how quickly and reliably tasks like debriefs and post-mortems get done, and where your post-mortems currently sit, from never opened through to completed.

You can now:

• See what proportion of flows or tasks are complete with a new ratio chart, and compare across custom fields like team
• Check completion rates by task type, so you can tell whether you're consistently getting a group of tasks (like post-mortems) done
• Understand how consistently your team is writing and reviewing post-mortem documents

Webhook delivery logs for workflows

We now record every webhook a workflow sends, so you can see exactly what happened and debug any errors you’re experiencing. You'll find this in two places: when you open a specific run in workflow activity, or when you edit a webhook step in the workflow editor.

We keep the full request and response for 7 days, and redact any secrets or Authorization headers.

Scribe and the agent can see in-call chat

Previously, Scribe only listened to what was said on a call, and missed things dropped into the call chat — like a dashboard link.

We now include in-call chat in the transcript, so Scribe can include it in call notes and ‘key moments’ shared in Slack. The agent can also see the chat and use it to answer questions, or investigate your incident.

This works with no additional setup.

Recent escalations alongside escalation paths

When viewing an escalation path, we'll now show its recent escalations on the right-hand side, so it’s easier to understand how a path is being used.

We’ll also show you this information when someone goes to delete the path, so it’s easier to see if something’s relying on a given path before removing it.

Smoother PagerDuty migrations

We've made it easier to import PagerDuty schedules and escalation policies

• PagerDuty Teams now automatically have members, making them eligible as team types without any changes
• When switching to a team type that doesn't have an escalation path attribute, we automatically create it
• When importing escalation policies, we automatically assign owning teams, making alert routes much easier to set up
• We've added support for the PagerDuty V3 Schedules API, so we can import schedules we previously couldn't

There's also a new in-app guide that points you to next steps once you've connected PagerDuty to help get started

Saved views for alerts on mobile

You can now view your saved views for alerts on mobile. These are view-only on mobile — you can't create new ones there, but any you've built on web are available to open, for both organisation-level and team-level views.

We've also added filtering of alerts by attributes so you can filter by team, feature and more.

Alert pulse channels can group alerts

If you have an alert route with grouping enabled and send messages to Slack or Microsoft Teams, you can now opt into having those pulse messages reflect your alert groups rather than posting each alert individually. The first alert posts as a regular message; when another alert joins the group, we turn it into a group message summarizing the number of alerts and their status.

What else we've shipped