July 2026 Summaries
6 posts from PagerDuty
Filter
Month:
Year:
Post Summaries
Back to Blog
ServiceNow serves as the backbone for IT operations in many enterprises, managing workflows, compliance, and incident tracking, while PagerDuty enhances this setup by optimizing incident response and resolution. Together, they provide an end-to-end operational resilience solution, with ServiceNow handling governance and PagerDuty focusing on real-time crisis management. The integration of these two platforms leads to faster incident resolution, reduced noise, fewer incidents, and increased automation, enhancing the overall value of an organization's ServiceNow investment. Organizations often have both platforms but may not fully utilize their potential when they are not integrated. PagerDuty's integration with ServiceNow is designed to be seamless, offering two-way synchronization that keeps both systems updated in real time. This synergy allows for AI-led, automated incident resolution, reducing the need for human intervention in routine issues and enabling teams to focus on more critical problems. By leveraging this integration, organizations can achieve significant improvements in operational efficiency and return on investment.
Jul 04, 2026
1,037 words in the original blog post.
PagerDuty has introduced an updated Shift-Based Scheduling tool to accommodate diverse on-call responsibilities more effectively, reflecting the varied ways teams manage their schedules. This tool provides solutions for custom on-call schedules, such as ignoring weekends, implementing week-on-week-off rotations using an "Unassigned" user, and managing multiple team members with different schedules. The Shift-Based Scheduling feature allows for the creation of custom schedules and rotations, facilitating flexibility without complexity, and offers options like creating overrides for when the entire team is unavailable. Users are encouraged to explore these new capabilities and contribute their scheduling challenges for further assistance on the PagerDuty Commons platform.
Jul 03, 2026
1,140 words in the original blog post.
AI coding tools have evolved from assisting developers with suggestions to independently writing entire modules and services, leading to increased complexity in software operations. The 2026 State of AI-First Operations report highlights that 84% of organizations are using AI for coding, but this rapid adoption also raises the potential for failure, with 68% of organizations experiencing significant financial losses during major incidents. As AI-driven development introduces new challenges, such as undetectable errors like "hallucinations" in code, the need for improved incident response and operational resilience becomes crucial. Organizations that invest in faster recovery processes are gaining a competitive edge, with 95% acknowledging the strategic importance of swift recovery. Despite the potential for AI to free up time for innovation, the majority of developers still spend significant time on incident response. Companies that systematically turn incidents into learning opportunities see improved resilience, but only 48% currently do so, highlighting a growing gap as AI complexity increases. Solutions like PagerDuty aim to manage this complexity by integrating AI throughout the incident lifecycle, transforming incidents into intelligence to enhance system resilience.
Jul 02, 2026
873 words in the original blog post.
PagerDuty's AI Orchestrations is designed to transform operations from reactive to proactive by automating event orchestration without requiring deep platform expertise. This capability analyzes historical event and incident data to provide recommendations for event orchestration rules in plain language, offering a global recommendations view ranked and filterable by team. The system suggests rules for alert suppression, severity setting, and incident prioritization, with each recommendation including impact metrics and a precision score for validation. AI Orchestrations operates after existing manual rules, allowing teams to apply or dismiss suggestions to refine future recommendations and facilitate automation adoption. This approach aims to reduce incidents, noise, and operational costs, contributing to PagerDuty's vision of Autonomous Operations by enhancing human judgment at scale. The feature is currently available for PagerDuty AIOps customers, particularly benefiting teams overwhelmed by manual alert triaging and low event orchestration adoption.
Jul 01, 2026
500 words in the original blog post.
PagerDuty has introduced an agent app available in GitHub, aiming to streamline incident response and build toward autonomous operations by reducing context switching for developers. This integration allows live incident data, change correlations, and operational context to be directly accessed within pull requests, enabling developers to make informed decisions without leaving GitHub. The app provides features like surfacing active incidents and service health, querying past critical incidents, and running pre-commit risk assessments by utilizing PagerDuty's extensive data. It empowers developers to prevent incidents by evaluating risks before deploying code, thus enhancing operational efficiency. The initiative is part of PagerDuty's broader vision to provide critical operational insights directly within the tools developers use, and it is currently available for PagerDuty Advance customers through Early Access.
Jul 01, 2026
707 words in the original blog post.
PagerDuty's launch of Rundeck/Runbook Automation 6.0 represents a significant advancement toward achieving autonomous operations by modernizing the foundational infrastructure that supports automation in production environments. This platform update, built on Grails 7, Spring Boot 3, and Java 17, addresses the challenges of outdated technology by enhancing compatibility, security, and observability, while also resolving over 20 CVEs. By incorporating Java 17 and 25 support, native Prometheus metrics, and MySQL 8.4 compatibility, Rundeck 6.0 ensures that automation workflows remain efficient and aligned with the latest infrastructure standards. The updates enable streamlined incident response and execution across diverse environments through a distributed Runner architecture, which provides secure automation without requiring direct network access to sensitive infrastructure. By addressing specific gaps and removing technical debt, Rundeck/Runbook Automation 6.0 empowers teams to focus on innovative development while maintaining robust and reliable automated operations that integrate seamlessly with modern observability stacks and security protocols.
Jul 01, 2026
778 words in the original blog post.