Commons Corner

Hi Folks!I’m on call for Incident Command here at PagerDuty part of this week, and I was wondering if you have a ritual or process for what you do when those alarms go off. I confess, after having been on call for various types of production systems over the years, that my first stop after ack’ing an alert is to stop in the bathroom - if you need to or not, just like Mom used to tell you on road trips. Then I make sure I have a beverage. The call might be long and require a bit of talking, so I want to have something to drink. Then I’m ready to go after that incident for however long it takes. Fortunately our incidents at PagerDuty aren’t nearly as bad as some I’ve been in for past jobs, where calls would run so long the battery would run out on my phone. But it pays to be prepared!What do you need to get you through an incident? I’d love to hear what keeps you going.  --mandi 

Hi everyone,I’m part of a IT team working to unify our incident response with infrastructure automation, and we’re exploring better ways to integrate tools like Ansible, Rundeck, or Attune with PagerDuty for real-time operations.Here’s what we’re trying to achieve: Automatically trigger predefined scripts or runbooks (via Rundeck or Ansible Playbooks) when certain PagerDuty alerts are fired Create custom PagerDuty services for various infrastructure tiers (e.g., DB layer, web servers, networking) with tailored responses Ensure clean logging, rollback, and audit trails for all automated responses triggered by PagerDuty incidents Tie notifications to team roles or escalation policies based on specific server groups or alert types Has anyone here successfully set up something similar?We’d love to hear: What integration method worked best for you (webhooks, APIs, plugins)? Any challenges around permissions or security controls when executing remote tasks post-incident? Advice on

Today’s GCP outage is hitting hard. We see you. We’ve been there. If you're on-call, in the incident room, or just trying to keep your systems afloat, this one's for you. Here are 6 tips to help you survive days like today.👇 1. Breathe.Before you dive in, pause. Stay grounded. Clarity matters more than speed when everything’s on fire. 2. Triage, Don’t Troubleshoot Everything.Find the impact surface first. What’s customer-facing? What’s internal? Prioritize based on real business impact. 3. Use the Buddy System.Nobody should suffer alone. Assign a comms lead, a responder, and a runner. Rotate. Burnout is real. 4. Use Runbooks & Checklists.Now’s not the time to rely on memory. If you’ve got docs, use them. If not, write down what you learn, future you will thank you. 5. Communicate Early and Often.Don’t go dark. Internal teams and customers want updates, even if it’s “We’re still investigating.” Silence creates chaos. 6. Debrief After, Kindly.Postmortems aren’t blame sessions. They’

Walking into a tech conference hall can be overwhelming. Tons of exhibitors trying to catch your attention with the latest industry trends, and you only have 30 minutes between one talk and the next, or that important networking meeting you’ve scheduled.Why not ask for a little help from your AI friends to use your time wisely and go straight to the booth that will show you what is really important for your operations?That's exactly what this PagerDuty customer did during AWS Hamburg this week. 👀 Look what they got:  

🚀 Check what’s new in PagerDuty and come back to let us know…

Version 5.12.0 is here! This version includes a smarter and improved HTTP response validation plugin, giving you greater flexibility to define what a successful response looks like in your automation workflows. Read the release notes for more information. Join our livestream to learn more about this release from our team, on Thursday May 29TH via Twitch, LinkedIn or Youtube.Plus, are you going to AnsibleFest / RedHat Summit in Boston? Come to our Tex-Mex fiesta 5/20. Sign up here.

We're excited to invite you to two webinars that explore how AI is revolutionizing system reliability and on-call practices.🔧 AI-Powered Developer Productivity: Building Self-Healing SystemsFriday, June 27 -  8am PDT | 11am EDT | 4pm BSTIs vibe resilience a thing? Not yet, but we’ve got to give it to AI – it’s changing the game. From AI-assisted triage to agents running automation, there’s a whole world of opportunities to rethink how our systems can be improved.We’re hosting a panel of PagerDuty thought leaders who will share how we’re thinking about AI transformation at PagerDuty, boots on the ground.Panelists:Moderator Mandi Walls, Senior Developer Advocate Rich Lafferty, Principal Site Reliability Engineer Scott Bastek, Applied Scientist Marlin Scott, Director, Software Engineering  🤖 Demo Roundups! On-Call Culture in the Age of AIThursday, July 24 -  8am PDT | 11am EDT | 4pm BSTHear from practitioners how AI is revolutionizing traditional on-call practices and incident managemen

💫 Early Access for ‘PD-Advance- Shift Agent(aka Intelligent Override Management)’ will begin Mid May! 💫💚 Open to all Incident Managent customers. 💚Please sign up here! Feature Details: Responders use PagerDuty's override functionality to update on-call schedules based on responders unavailability. Manual Overrides are time consuming due to requiring multiple manual steps, collaborators, and conversation to complete across different surfaces. Furthermore, On-call shifts are the last thing on a responder's mind when preparing to be out of office. Thus creating risk for missed management.With the PagerDuty’s Agentic AI functionality, the Shift Agent will take the toil out of override management. With the Shift Agent, PagerDuty will consume Responders vacation/out of office (OOO) from manual input, APIs, and calendar/HR Integrations - Integration Release Dates: Google Calendar in July and Workday in November   If an OOO conflicts with a responder’s on-call schedule, PagerDuty will noti

Hi there, drop your intro in this conversation ⬇️Tell us:Who are you? What do you do? What are you looking the most forward to in this meetup?Looking forward to meeting all of you! ➡️ Event Details

This release addresses three critical issues that were identified in versions 5.11.0. The fixes focus on improving runner functionality and key storage UI bugs.Resolved an issue where changes made to runner node-filters were not being saved properly. Fixed the non-functioning key storage selector when using runner. Addressed a bug where persistent error messages in runner logs stating "Runner did not deliver reports in the configured timeout period" and resulted in jobs not continuing to run.Please check the release notes.Rundeck / Runbook Automation 5.11.X includes a new MongoDB plugin for database automation, plus enhanced SQL query output options to view in multiple formats. Read the release notes for more information.

🚀 Check what’s new in PagerDuty and come back to let us know…

Step into a smarter way of working with PagerDuty's AI-powered platform.Experience how intelligent automation and predictive insights help teams evolve beyond incident response to deliver consistently superior customer experiences. https://pagerduty.navattic.com/aiops

Experience how PagerDuty transforms incident communication through unified stakeholder management. From setting up Business Services to creating targeted Status Pages, learn to keep both internal teams and external customers informed with real-time, secure updates. Discover the art of delivering tailored communications to different audiences while maintaining a single source of truth for all incident updates.Click here!

Hey everyone, drop your intro in this conversation ⬇️Tell us:Who are you? What do you do? What are you looking the most forward to in this meetup?Looking forward to meeting all of you! 

CTO from CloudZone learning from PagerDuty’s experience with Agentic AI for reducing MTTR

Our open-source API client for Python has now been refactored from a monolithic one-file module into a multi-file module. This change is being made to fulfill a need for long-term maintainability and improved readability. This new release does not add new features, but aims to make contribution of new features far easier going forward, most notably enabling us to add a py.typed file to enable using typehints in projects (issue #26). More about this release:https://github.com/PagerDuty/python-pagerduty/releases/tag/v2.0.0https://pagerduty.github.io/python-pagerduty/changelog.html