Get Involved

Hey Community.  We held our Toronto PagerDuty User Group yesterday and wow, what a great turnout and great topics we had. We had a zoom conference running but to be honest, we didn’t have any one really join via zoom, which is probably a good thing.  These user groups should be done in person. What are your thoughts on PagerDuty User Groups? Do you want one in your city/region?  Do you agree it should be in person?  

The PagerDuty MCP server now delivers deeper incident triage and event orchestration details via newly added APIs, enabling AI assistants and agents to access key PagerDuty data including outlier incidents, past incidents, related incidents, and service/global event orchestration configurations.   View the full session 👈🏾 Resources:- MCP API Documentation: https://developer.pagerduty.com/api-reference/d71edf8527b5e-pager-duty-mcp-api- GitHub Repository: https://github.com/mcp- GitHub MCP Registry: https://github.com/mcp 

Hi everyone,We sincerely apologize for this morning's technical issues that prevented registrants from joining the live webinar with Arize. The full recording is now available.Since you couldn't ask questions live, we've created this thread for Q&A. Our speakers are ready to answer your questions about AI reliability, monitoring, observability, and implementation strategies.How to participate:Watch the recording Post your questions in the comments Get answers directly from our speakersWhether you want to dive deeper into specific topics or discuss how to apply these concepts to your organization, ask away! 

Are you passionate about building resilient systems or have a story to tell about managing incidents in creative ways? We want to hear from you! We’re excited to announce the Call for Papers is officially open for PagerDuty on Tour San Francisco 2026. This is your chance to showcase your innovative ideas, share real-world lessons, and connect with a vibrant community of peers and industry experts.Session Guidelines:Session format: Talks (20-30 minutes including Q&A) or Panels (40 minutes moderated discussion) Session topics: Back to Basics, Building resilient systems and teams, Automation and AI in operations, and more - see full list of topics in the submission form Audience: developers/SREs - we recommend providing at least three actionable takeaways fit for a technical audience.Ready to submit your idea? Submit your proposal here by November 14th and help shape the future of incident response, automation, and reliability.We can’t wait to see what you’ll bring to the stage. 

UPDATE - September 16, 2025: Shift Agent and Scribe Agent are generally available! Learn more here. All new PagerDuty’s AI Agents are in Early Access: Shift Agent, SRE Agent, Insights Agent and Scribe Agent!Are you ready to bring AI-powered incident response to where your teams work? If you're selected for our Early Access program, you can get your hands on some of our latest and forthcoming innovations—and your feedback will help us deliver a better, more valuable product experience to all our users.Apply now for the chance to access and help us build the PagerDuty you want to use.Watch a sneak peek of our Product Managers showcasing how these AI agents can transform your incident management workflow by:🌟 Eliminating manual steps🌟 Providing data-driven recommendations based on past incidents🌟 Delivering proactive metrics🌟 Streamlining documentation processes  Catch the full webinar on-demandShift Agent: Ask the agent about your on-call schedules and upcoming shifts, automatically

Today at 4PM GMT | 8 AM PDT | 11 AM EDT we will host the Learning MCP with PagerDuty live stream  This post, is for sharing all the resources mentioned throughout the stream, as well as for you to ask any follow up questions or share related content that might be relevant for the conversation!  See you all later today 😁

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

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

Hello, I have written an open-source .NET library which is a client for the PagerDuty Events API V2. Repository on GitHub Package on NuGet Gallery It’s focused on being up-to-date with the latest V2 API, comprehensive documentation, handling both sending changes and triggering/acknowledging/resolving alerts, easy configuration, easy calling, and the ability to mock it in automated tests. I have been using it for 18 months so far in programs that notify me when my laundry is done, and it has been stable. Feel free to include it in the API Client Libraries table if you wish. Thanks!

Hi all, especially Python users,Given the nature of PagerDuty the product and its APIs, some basic use cases are sufficiently useful and near ubiquitous, making them too important to not implement. For these use cases I am considering breaking a convention of “not making an API for the API”.*A few features in this category that I’ve been considering:Fetch incident notes Create overrides, for all on-call shifts of a given user and time period to another user (or round-robin the shifts among a group of user IDs) Fetch all historical records from all time (i.e. log entries), using a shifting time window to avoid hitting the pagination limit Add abstraction for the bespoke pagination styles of: POST /analytics/raw/incidents GET /alert_grouping_settings Which of these do you think would be the most useful and save the most time? What more general automation use cases do you believe are worth building an opinionated method into an API client that in this area has previously been un-opiniona

Calling out all Rundeck by PagerDuty open-source experts out there!We’re gearing up for next Rundeck by PagerDuty meetups (in-person & virtual), and we want YOU to be one of our rockstar speakers! If you’ve got some cool insights, epic stories, or game-changing tips about your experience with Rundeck by PagerDuty open-source, we’d love to hear from you. This is your chance to shine, share your knowledge, and inspire your fellow community members. Plus, it’s a great way to network and connect with like-minded folks in the industry!If you’re interested (and we hope you are!), visit https://github.com/rundeck/rundeck-meetups, reach out to us at community-team@pagerduty.com, or leave a comment below and let us know your region, topic idea and availability. We can’t wait to make the next meetups the best one yet with your help!Watch a previous Rundeck by PagerDuty EMEA meetup with guest speakers Diego Infiesta from Ryanair and Hans Erasmus (@hans.erasmushe) from HBPS Consulting:  🎁 All