Commons Corner

Will you be at KubeCon + CloudNative North America in Atlanta this November 10-13?PagerDuty will be there, and we’d love to connect - whether it’s at our booth or during an exclusive happy-hour event! Drinks and eats on us! Register to attend our Happy Hour on Wednesday, November 12 Visit the PagerDuty Booth #455 for interactive demos, participate in the booth passport program, and enter our raffle to win a Pagey

 For over 16 years, PagerDuty has been trusted by 32,000+ organizations as the incident management leader, helping teams forge a path forward with modern operations.This launch is built around one principle: champion the customer. Here's what we built for you:🌟 The End-to-End Incident Management Features You've Been Waiting ForFlexible scheduling that fits how you run on-callModern Flexible Shifts

According to PagerDuty data, incident responders can spend 50% of their time just figuring out who to call and what's actually broken.Watch the latest Demo Roundups! session to see how automated diagnostics can slash your MTTR from 40 minutes to just 2 minutes.What you'll discover: ➡️ How to eliminate the manual triage bottleneck that's killing your efficiency➡️ One-click runbooks that give first responders expert-level diagnostics instantly➡️ Real results: reduced stress, exceeded SLAs, minimized after-hours escalations 👀 Watch a sneak peak:  📚 Resources shared during the session: Read on the Blog:

Ensuring stress-free on-call coverage and capturing complete incident records just got so much easier! Shift Agent and Scribe Agent are now generally available for all PagerDuty Advance customers! Both agents are designed to help you stay focused on what matters: resolving incidents faster, reducing manual toil, and keeping your team in sync. Shift Agent: Intelligent on-call conflict resolutionNo more scrambling to fill gaps or chasing down coverage. Shift Agent works right in Slack to:Share on-call schedules and upcoming shifts Automatically detect PTO conflicts based on PagerDuty Schedul

Hey PagerDuty community! 👋We experienced service disruptions on August 28 that affected some customers in our US Service Regions, and we owe you complete transparency about what happened.The overview: A Kafka system failure at 3:53 UTC triggered cascading issues that disrupted event processing for several hours. While no data was lost, some customers experienced 502 errors, delayed notifications, and degraded platform functions.Here's a sneak peek of what you'll find in our full incident report:Detailed technical breakdown of the Kafka failure and cascading effects Complete timeline from initial incident through full resolution How a second, smaller incident actually helped us identify the root cause Why our external communication was delayed (and how we're fixing that) Specific improvements we're implementing to prevent recurrence Lessons learned from our response and r

The transition from traditional monitoring technologies to modern observability tools can leave teams confused. Satbir Singh joins us to talk about the new goals of observability tooling and how it will help teams conquer challenges in complex systems.LISTEN HERE ⬇️ 🎧 Listen on Page it to the Limit or in your favorite podcast app: Spotify | Apple | 

What happens after an incident matters just as much as how you handle it.Anojan Gunasekaran, Senior Product Manager for Incident Analysis at PagerDuty, showcased how to transform post-incident reviews from a bureaucratic necessity into a powerful tool for organizational improvement.Learn how to structure reviews that help facilitate meaningful discussions, identify systemic issues, and create actionable recommendations that prevent future incidents.👀 Watch a sneak peak:  📚 Resources shared during the session: Read on the Blog:

Today’s episode is about technical debt, not as a cautionary tale, but as a lens. We take a closer look at where debt comes from, how it quietly rewires teams, and why paying it off is rarely just a matter of “cleaning up code.” Along the way, we’ll examine two real-world stories: one where unaddressed debt led to a $440 million disaster, and another where a company used an infrastructure overhaul to rebuild architectural trust. This is about more than code. It’s about momentum, memory, and the systems we inherit.  🎧 Listen on Page it to the Limit or in your favorite podcast app: 

Alert fatigue can happen to anyone working in environments with a lot of signals from different sources. In security, teams are dealing with potential threats reported by tools running across the organization. Dealing with all the alerts, whether they are positive, negative, false positives, false negatives, is a lot of mental stress and requires cognitive capacity that can be depleated. In this episode, we speak with Boaz Barzel, Field CTO at OX Security, about his research on the subject.Boaz Barzel is the Field CTO at OX Security, specializing in bridging the gap between security, technology, and business. By making tech makes sense, Boaz is aligning product innovation with the real-world needs of customers and is known for transforming complex security challenges into strategic business advantages. With extensive expertise in application security and product innovation, he ensures security solutions are not just reactive but proactively address emerg

Welcome to the future of operations, where people and agents manage critical work together, driving productivity and efficiency. Learn how PagerDuty’s AI agents can supercharge teams, by autonomously handling repetitive tasks and resolving well-known issues, while surfacing data and insights that augment human expertise for faster resolution and higher operational resilience.🎤 Host: Mandi Walls, Senior Developer Advocate at PagerDuty🎤  Guests: PagerDuty’s Brita Seltzer (Director, Product Management), Débora Cambé (Product Marketing Manager), Jacky Leybman (Principal Product Manager), Julia Nasser (Principal Product Manager), Mya King (Senior Product Manager) 👉 WATCH ON-DEMAND: Demo Roundups! Meet the PagerDuty AI Agents

AI used to wait for instructions. Now, it doesn’t always ask. In this opening episode, we explore the rise of agentic AI systems that don’t just respond to input, but take initiative, set goals, and act on their own. We break down what agentic really means, why it’s different from traditional automation, and what kinds of design and trust challenges this shift introduces. Along the way, we look at how this plays out in tools that summarize, schedule, and trigger real-world workflows — and why autonomy sounds good in theory but gets messy fast. Whether you’re building LLM-powered copilots, evaluating autonomous workflows, or just trying to keep your incident response human-aware, this is the groundwork you’ll need for what’s coming next.Sid Verma is a Developer Advocate at PagerDuty, where he helps developers optimize their workflows and implement scalable solutions. With a deep background in observability, DevOps, and enterprise open source technologies