Recently active topics

Hi everyone! 👋I’m Gurnish, a software developer from Gurugram, India. I primarily work with React and Vue, and lately I’ve been exploring backend systems and authentication flows as part of building an IAM (Identity & Access Management) platform.I came across PagerDuty while trying to better understand how real-world systems handle incidents, alerts, and reliability at scale. I’ve been exploring the platform and really like how it simplifies incident management and makes complex workflows easier to handle. It’s been interesting connecting these concepts with what I’m building and learning about system design.Looking forward to learning more from the community and contributing where I can! 🚀

Hello!Today we have one person on call from our department to handle incidents. We share this schedule amung us and we try to resolve incidents at our best abilities. That is ok.But during the work hours we would like the incident to go to the subject matter experts directly.I manage to get this to work by creating escalation policy and schedule for each subject, and restricting the schedule for work hours only, and duty watch as level 2 on the escalation policy.But this means that everyone gets a on call and off call alert every day. This is annoying. Each user can disable this I believe, but it is useful for the duty watch schedule.Any suggestions? :)

Hi PagerDuty community,I'm developing a mobile app for Ubuntu Touch in Python and QML to manage PagerDuty incidents, using the python api library (https://github.com/PagerDuty/python-pagerduty).I ran into a limitation when trying to implement notification.Currently, PagerDuty does not natively support UnifiedPush (https://unifiedpush.org), an open standard for push notifications that works independently of proprietary services like Google's FCM or Apple's APNs. This makes it impossible to receive real-time push notifications on platforms such as Ubuntu Touch, as well as on any other FOSS-friendly distribution i.e. where Google Play Services are not available.Would it be feasible for PagerDuty to add UnifiedPush support on the backend side?Concretely, this would mean allowing users to register a custom push gateway endpoint (a UnifiedPush distributor) instead of relying solely on FCM/APNs. The notification payload would then be forwarded by PagerDuty to that endpoint, and from there to

I’m working on designing an Enterprise-level incident response and management system for our client using PagerDuty. We’ll be using the Enterprise edition and would like to understand the implications if PagerDuty were to go down. I know that PagerDuty is a SaaS service with a 99.99% uptime guarantee. In a worst-case scenario, for instance, if AWS were to experience a downtime, would PagerDuty also be affected? I need to design an alternative solution for this scenario as well. Additionally, I’m curious about how to determine which escalation actions were taken and which were not. Anyone has some thoughts? If you have worked on similar scenario, how did you approach that?

PagerDuty Incident Workflows, the built-in Delay action requires the duration to be specified in the format of XXd XXh XXm, with a minimum delay of 5 minutes, Can we please update this and allow Delay in Sec? with minimum 5Sec? 

PagerDuty’s Slack integration turns on “Chat message ingestion” and “Privatechannel ingestion” by default so that it can suck up as much info as possible from Slack chats, even though it’s totally unrelated to the integration itself. The only way it allows to turn these off is to email support@pagerduty. However, I sent them emails 6 and 8 days ago, and still no response. Is there any way to get support to do anything? Or should I just assume that they won’t?

We get a published rotation of people covering the next 30 days from an outside vendor so the schedule changes every month. I don’t see an end date for a layer. - like starts Monday 3/16 and ends Friday 3/20. Right now the schedule just repeats ad nauseam even though we don’t have the schedule for April yet. Our old paging system allowed Start On and End On dates. Does PagerDuty have that mechanism?

Created our first Custom Field on a Service, a single select list to identify the Engineering Team responsible for that Service. I was hoping that we could set it up in a way so that when a responder receives an alert for a new Incident, since each Incident is paired with the appropriate Service, we could also display that Engineering Team custom field on the Service, at the Incident level. However, in reality it appears that the Custom Field on the Incident is not related in any way to Custom Fields on the Service.  Is it possible for me to display custom fields asociate with a Service, on incidents related to that service, so that on-call responders can see that info and I don’t have to manager an entirely separate custom field at the Incident level? Thanks! 

Hello everyone !Using Rundeck for a while (~2020), managing 2 instances for my company, here to lurk some information about issues, fix, problems and solutions of course ! Have a nice day !

have a nice day with rundeck :)  🙂 

Catching up on the last two weeks + what's coming next🎉 Recent HighlightsPagerDuty On Tour - LondonPagey claw machine at our Play ZoneOur flagship event brought together 160+ attendees for an incredible day! PD Commons ran a Play Zone featuring a Jeopardy game that had 40 people competing—including a customer who's been with us for 14 years! Missed it? Check the speaker lineup on Commons.DevOps Not Dead Conference - LondonDaniel Afonso (aka sir Page-a-Lot) took the stage in full knight armor 🛡️ to deliver his talk on The State of AI in Incident Response. When the conference theme is fantasy, you commit to the bit.AWS User Group Lisbon x Cloud Native Lisbon MeetupOur Lisbon office hosted Debugging & Incident Response in the Cloud Native Era with 60 registered participants. The energy was high—folks stayed until 10pm, demolished 22 pizzas, and cleared 3 boxes of beer. That's what we call a successful meetup. 🆕 Product & Partnership NewsSpring '26 ReleaseIntroducing the Path to

good good good

Hey Community! 👋We all know the pain of "noise"—the alerts that don't matter, the context-switching that kills focus, and the manual toil that keeps you from building cool stuff.To help, PagerDuty University is running a 6-part deep dive into AI-Powered Operations. We’re skipping the high-level fluff and getting into the "how" of building a more resilient, automated operating model.Each 30-minute session covers a specific pillar: Noise Reduction: How to actually get to the root cause without the static. Accelerated Response: Using AI to automate the "boring" parts of the incident lifecycle. Resilience & Compliance: Best practices for scaling your ops without losing control. Whether you're looking to optimize your current setup or see what the latest AIOps features can actually do for your workflow, these sessions are built for you.👉 Check out the session lineup and grab a spot: https://university.pagerduty.com/page/ai-powered-webinar-series

We're excited to announce our latest release focused on autonomous operations – transforming how teams handle incidents with AI-powered capabilities built on 16 years of operational intelligence.What's New:SRE Agent as a Virtual Responder – No more 3 AM wake-up calls. Add SRE Agent directly to schedules and escalation policies as your first line of defense. It detects, triages, and diagnoses incidents before paging humans, with full control over permissions and remediation approvals. Plus, it learns from past incidents to continuously improve.Coming soon: SRE and Insight Agents for Microsoft Teams, enhanced Scribe Agent with conference bridge chat ingestion, and AI agents available in the Web UI.Full Lifecycle Incident Management in Slack & Teams – We're eliminating context switching with dedicated incident channels, threaded updates, and SRE Agent embedded directly in-channel. Our modernized Slack experience is live now, with Microsoft Teams enhancements rolling out soon, plus pre