Welcome to PagerDuty Commons

PagerDuty User

Ability to "Raise urgency of unacknowledged incidents to high"

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.

3075

New PagerDuty Runbook Automation Learning Path and Certification

rachel laycookDutonian

PagerDuty University

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.

100

PagerDuty at KubeCon + CloudNative North America – Booth #455 & Happy Hour Event

xamiciCommunity Manager

Announcements

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 Lego set!

180

5 days ago

sky320New Member

The lookup plugin 'nios_next_ip' failed: a bytes-like object is required, not 'str'"

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<&

101

msaeedNew Member

OpsGenie user - so difficult to manage Pagerduty - Escalation policy etc

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.

151

Call for Papers Now Open: PagerDuty on Tour San Francisco 2026

dlee1Dutonian

Announcements

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

360

9 days ago

jlarrimoreNew Member

GET incidents based on update_at timestamp

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.

804

10 days ago

PagerDuty Community TeamCommunity Manager

Announcements

Product Launch: Delivering Over 150 Items You've Been Asking For

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 (forthcoming EA for IM and CSOps plans) - Create intuitive iCal-based recurring shifts that eliminate the complexity of layers entirely, with support for multiple responders per shift, shadow schedules for backup coverage, and automatic conflict detection. Shift Agent (GA, PagerDuty Advance customers) - Handle on-call conflicts and overrides directly in chat with AI-powered recommendations.Core incident management enhancementsRequired Fields on Resolve (EA for IM and CSOps Enterprise plans) - Ensure critical data is captured before incidents can be closed. Reopen Incidents (GA, IM and CSOps

210

10 days ago

Olivia Mo

Preserve incident acknowledgements list after it has been resolved/triggered

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

414

17 days ago

PagerDuty

Ask product questions, access official documentation, give feedback and suggest new features

Ask a product question

411 topics

Commons Corner

Introduce yourself to the community, keep up with all things community and PagerDuty, share tech-related jokes and celebrate outstanding community members

Introductions

6 topics

Announcements

110 topics

Get Involved

10 topics

Community Spotlight

8 topics

PagerDuty University

10 topics

Ops.lol

10 topics

Starting with PagerDuty

Onboarding materials and best practices for new PagerDuty users, admins and managers

About the Community

4 topics

PagerDuty User Onboarding

39 topics

How-tos & Best Practices

8 topics

rachel laycookDutonian

PagerDuty University

New PagerDuty Runbook Automation Learning Path and Certification

100

sky320New Member

The lookup plugin 'nios_next_ip' failed: a bytes-like object is required, not 'str'"

101

msaeedNew Member

OpsGenie user - so difficult to manage Pagerduty - Escalation policy etc

151