Access a live, unified view of incidents across services. Quickly identify blast radius, service impact, and detect anomalies by visualizing incidents across time. Service Health Visualization enables faster decision-making and triage at scale by bridging the gap between observability and incident response. Now you can focus troubleshooting in one place with customizable filtering and contextual overlays. Early access available to all customers who have Operations Console.
This feature analyzes configured Incident Workflows and evaluates them against the real-time context of each incident. The SRE Agent then intelligently recommends the most relevant workflow to run, ensuring faster, more precise, and context-aware incident response. Sign up for Early Access.
Japanese conversations with SRE Agent in Slack can be enabled via user voice language settings from PagerDuty or via automatic language detection from Slack messages.
The latest MCP enhancements provide richer incident and alert context through expanded capabilities. Engineers can now:
- Retrieve detailed incident log entries with get_incident_log_entries
- Access additional incident data using enhanced query parameters in get_incident
- Inspect alert details using list_alerts_from_incident and get_alert_from_incident
Additionally, list_users now supports including contact method data, enabling responders to reach the right person faster. Learn more about PagerDuty MCP here .
Incident commanders can renotify responders who may have missed the initial alert and cancel pending notifications when circumstances change, directly from the incident timeline. This ensures critical issues never go unnoticed, reducing MTTA/MTTR and preventing service degradation from unattended alerts. Learn more or watch this short demo video.
We've updated our Slack integration with three key improvements:
- New slash commands for quicker access to PagerDuty Incident Management actions.
- Redesigned incident cards with updated emojis and clearer information hierarchy.
- Threaded updates to reduce channel noise. Incident updates now appear as threaded replies by default, keeping your channels organized.
Learn more here.
We are no longer proceeding with the Postmortems End-of-Life that was previously scheduled for January 30, 2026. You can continue using Postmortems.
SRE Agent can intelligently deduce the next steps for troubleshooting issues by retrieving log data from New Relic. Using observability data, the SRE Agent can guide responders through investigative, triage and resolution steps - ultimately reducing MTTR and escalations. Learn more.
Configurable from within language settings, the Operations Console is now available translated to Japanese. Sign up for early access here.
Incident Workflows enable you to automate your incident response processes. These workflows can be triggered automatically through Conditional Triggers. The product limits for Conditional Triggers have been increased so that 40 Conditional Triggers (previously 20) can be associated with a given Technical Service and 20 Incident Workflows (previously 10) can have Conditional Triggers that apply to all technical services. Full details on Incident Workflows and Conditional Triggers can be found here.
