Recently active topics

Hi! I was just added to my organization’s PagerDuty rotation, and after setting up the iOS app on my phone and testing out the notifications, I discovered that I cannot adjust the volume of the high-urgency notifications, which are sent as native Critical Alerts. A quick Google for “ios critical alerts volume” shows that controlling the volume of these alerts is not possible as an iPhone user, but it is possible as an app developer; this blog post shows something called “PushOver” allowing users to configure Critical Alert volume on a scale of “loud” to “deafening”. “Deafening” is how I would describe the current volume level of the high-urgency notifications, and this is just not acceptable in my situation: I’m not the only person in my building, and I can hear these notifications outside on the street, two-stories down 😅. I understand their importance, but the whole apartment building doesn’t, and I’m sure to run into problems with the neighbors if I turn these on. Can you pl

I’m not sure if anyone encountered similar problem.We just suddenly cannot receive any webhook of pagerduty from Sep26,  the endpoint is definitely reachable and had been working for years.I can see the webhook integration of most services had been disabled,  if I manually enable them , they just got back to be disabled almost immediately.it did happen around my yearly renewal ,so I wonder if it’s something to do with that.

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! 

I am configuring a new PD service where “Outside support hours” is set to “Dynamic notifications based on alert severity”. If severity is “high” the on-call engineer gets paged, otherwise it will be considered as low urgency. Up to this point all good. However, I want the alert to be raised to high urgency once we enter support hours. This is possible when “Outside of support hours” is set to “Low-urgency notifications, do not escalate” as there’s a check-box “Raise urgency of unacknowledged incidents to high” I can tick. Why is this checkbox not available when I select "“Dynamic notifications based on alert severity”? Let me know of an alternative approach. I wanting to avoid having to create 2 services for this.

Exciting news for RBA users!PDU has revamped our RBA learning path! 🚀  Whether a user is new to automation or looking to deepen their expertise, this learning path guides users from foundational concepts to advanced operational controls—empowering them to design, deploy, and manage resilient automation at scale.Even more exciting news: We have launched our PagerDuty Runbook Automation Certification!  All users that have access to certifications will see this certification in their PagerDuty University account.  Check out the one-pager about this new certification here, and the study guide for the certification exam here. 

Hello when attempting to run a ansible play via bash script on a remote RHEL 9 node i am getting "ERROR]: Task failed: Finalization of task args for 'ansible.builtin.set_fact' failed: Error while resolving value for 'infoblox_next_ip': The lookup plugin 'nios_next_ip' failed: a bytes-like object is required, not 'str'". This play is using the infoblox plugin to lookup ip addresses, it works great if i run on the remote node local CLI however when triggered from rundeck to the RHEL 9 node i get this error. From my testing it appears to be related to the password and special characters but im not 100% sure. Any ideas on how to troubleshoot?Not working(trigger from rundeck): rundeck -> shell script -> ansible-playbook -> infoblox moduleWorking(local CLI on RHEL Node): ansible-playbook -> infoblox module250 - name: Get next available IP address in given subnet with exclusions251   ansible.builtin.set_fact:252     infoblox_next_ip: >-                          ^ column 23<&

I am new to pagerduty. Trying to set up alerts and escalation policy. nothing seems to work at all. I have set escalation policy repeat alert 9 times if no one acknowledges. and guest what after that change I stop getting any kind of alerts even if I acknowledged it whilst alert is still firing from grafana side.  I doesnt repeat any alert at all for some reason and also creates incidents in a single payload. Why would I want all incidents in one payload. Also do you have feature when alert closes itself once it stops firing from grafana side like it happens in opsgenie. 

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, taking place on March 3rd, 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 October 31st and help shape the future of incident response, automation, and reliability.We can’t wait to see what

Hey all, I’m utilizing the /incidents API to fetch all incidents for an internal report. From what I can tell the since/until date parameter is filtering based on the created_at date. Does anyone know if there is a way to filter based on the updated_at field? I’d like to incrementally load a warehouse with the incidents from this API, but you can’t really do that if you can only filter by the created_at date.  

Hi, in the get incidents api the list of acknowledgements gets cleared after it has been resolved/triggered, why is that? Can we please preserve the list of acknowledgements, we need this data for our reporting

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

Hello,Am trying to setup rundeck :4.11(with customized docker image) with MySQL azure:8.0.42 as database.Am struck with the liquibase below error:Issue:“Caused by: liquibase.exception.MigrationFailedException: Migration failed for change set core/WorkflowWorkflowStepPrimaryKey.groovy::1653585641550-1::rundeckuser (generated):     Reason: liquibase.exception.DatabaseException: Incorrect table definition; there can be only one auto column and it must be defined as a key [Failed SQL: (1075) ALTER TABLE poc_rundeck.workflow_workflow_step ADD id BIGINT AUTO_INCREMENT NOT NULL PRIMARY KEY]        at liquibase.changelog.ChangeSet.execute(ChangeSet.java:696)”.  When I tried the same instance on flexible server database with MySQL:8.0.25, it is running without any error.I have done all the prerequisites mentioned in the official documentation regarding “sql_generate_invisible_primary_key > Change its value to OFF”, sql mode also off. But still getting the same error. (Using MySQL as a databa

For the past few weeks when I try to “acknowledge” an incident, it ends up snoozing it by default. I then get woken up 10 minutes later despite the acknowledgement. Very, very annoying. 

Hi PagerDuty team! 👋I'm trying to get custom details from Grafana alerts to display in our Slack notifications, but only seeing basic information.Current Setup:✅ Grafana → PagerDuty integration working (using Events API V2) ✅ PagerDuty → Slack integration connected (service: my-service-prod → channel: #team-alerts) ✅ Alerts are flowing through successfullyThe Issue: Our Grafana alerts send rich custom details to PagerDuty (verified in PagerDuty incident view):severity: "critical" namespace: "production" pod: "api-service-7d9c5-xyz" cluster: "us-west-2-prod" component: "api-service" description: "Pod is in CrashLoopBackOff state..." runbook_url: "https://wiki.internal/runbooks/..."However, in Slack we only see:🔴 Pod CrashLoopBackOff AlertService: my-service-prodUrgency: Low[Acknowledge] [Resolve]What We Need: Display the custom_details fields in Slack notifications so our on-call engineers can see critical context without clicking through to PagerDuty.What I've Tried:Configured PagerD

I am needing to create a DuPont schedule in PagerDuty and having a hard time.  Has anyone ever created a true DuPont schedule that can help?

Hi,Where I live, we use 24 hour clock, we start the week on Monday, and date format is dd.mm.yy. How do I select this in the web interface?I’m running on a EU instance, why is 12 hour format default?