August 2026 Summaries

PagerDuty’s Event Enrichment, available in Early Access, is designed to reduce incident-response delays by automatically adding operational, ownership, maintenance, and business-impact context from sources such as ServiceNow CMDB to incoming monitoring events. Its contextual data layer stores synchronized source data, while configurable enrichment rules, including account defaults and team-specific settings, match event fields to schemas and place relevant information in event details. Extract, Compose, and Connect Mode capabilities allow organizations to transform data and build reusable logic, enabling enriched information to drive orchestration before alerts are routed or responders are paged. This can suppress alerts for assets in maintenance, route incidents to responsible teams, and reduce reliance on manual investigations and hard-coded routing tables. PagerDuty positions the feature as a foundation for broader autonomous operations, supporting improved event correlation, automation, and future tools such as SRE Agent.

PagerDuty has expanded its SRE Agent, a virtual incident-response assistant designed to support autonomous operations by gathering cross-stack signals, applying knowledge from past incidents, and continuously learning from outcomes. New capabilities allow the agent to begin triage automatically through escalation policies or incident workflows, so responders can access investigation context before acknowledging an alert. Simplified connectors, tools, and custom skills extend the agent with observability, knowledge-base, and third-party data sources, while team-level permissions provide enterprise governance over AI access. The agent can also recommend appropriate incident workflows and explain its reasoning, helping responders assess its suggestions and build trust. PagerDuty describes an end-to-end process in which the agent investigates an incident, recommends and validates remediation, resolves the issue, and generates runbooks to improve future responses, with several enhancements currently available through general availability or early access.

PagerDuty has made Custom Field Mapping generally available for its plugins for Spotify for Backstage and Spotify Portal for Backstage, enabling teams to continuously synchronize service metadata from Backstage catalogs into PagerDuty incident workflows. The capability lets administrators map catalog fields such as service tier, ownership, runbook links, repositories, and dependencies to PagerDuty custom fields, giving on-call responders relevant context when incidents begin. Because the data remains structured and continuously updated, it can also support routing, escalation, search, filtering, and reporting. Teams can disable mappings to pause synchronization while retaining existing values or delete them to remove data from both systems. PagerDuty positions the feature as a step toward autonomous operations by using consistent service context to improve incident response, prioritization, measurement, and long-term prevention efforts.