September 2026 Summaries
2 posts from PagerDuty
Filter
Month:
Year:
Post Summaries
Back to Blog
PagerDuty has introduced PD Automation Runner in Early Access to extend automated incident response to on-premises and self-hosted environments, beginning with Kubernetes. Deployed within a customer’s infrastructure, the lightweight component initiates outbound connections to PagerDuty, allowing Workflow Actions and the SRE Agent to authenticate locally, gather diagnostics, execute approved remediations, and return results without requiring inbound ports, IP allow lists, or persistent external access. The company describes a workflow in which incidents can trigger automated pod analysis, log review, historical incident comparison, and recommended fixes that responders can approve for local execution. PagerDuty says the runner also captures diagnostic and remediation data to improve future SRE Agent recommendations across cloud and on-premises systems. Support for additional self-hosted tools, including Splunk, Grafana, and Prometheus, is planned.
Sep 02, 2026
640 words in the original blog post.
PagerDuty has introduced Scoped OAuth for Public Apps in Early Access to give administrators centralized visibility and control over third-party applications accessing their accounts. The feature replaces broad, difficult-to-track API key access with explicit, resource-specific permissions, allowing apps to request only capabilities such as reading incidents rather than full account access. Admins can review an app’s publisher and requested scopes before installation, approve or deny access, see authorized users, revoke individual or all connections, and fully uninstall apps when needed. PagerDuty positions the capability as a foundation for secure autonomous operations, where integrations, workflows, and AI agents increasingly act on data at scale and require transparent, approved, and rapidly revocable access.
Sep 02, 2026
656 words in the original blog post.