Ask a product question

I have an escalation policy -Now , I got an incident - Why did it not escalate even after 10 mins ?  if defined in escalation

Hi team,I noticed that PagerDuty no longer send mobile app push notification, phone call or text message when an alert is triggered. Is there any change during the last a few months on PagerDuty end? Thanks

Hello,Is there a possibility or has anyone tried to extract PD data of Alerts instead of Incidents for data collection? I saw some incidents that was merged automatically due to intelligent merging and I wanna know if I can extract alerts triggered instead of incidents

Hello, everyone! How to stop PagerDuty from paging onshore L2 (via phone) team after offshore L1 acknowleges the page (via email)? Thank you!

We’d like to see the metrics on the Dashboard (under the Over Time section) filtered by Business Services.Some of our business services have more than fifty technical services so it is impossible for the management teams to use it.On the Dashboard it should also provide a link to the Insights/(Business Impact), just like all the other sections do.

Hello folks,I would like to clarify whether I can trigger alerts by sending an email to PagerDuty or by calling support line. Does anybody know how can I do it? I am on a free plan.Thank you in Advance for your answers,

Our existing incident mgmt process includes an escalation policy which always initiates our product engineering team. The process rings through to several team members until someone joins the incident from that team. They would like to be the first initial single point of response to all incidents. However, sometimes they would like to reassign the incident to our cloud team. Is it possible to create an additional escalation policy which rings through to a set of individuals from our cloud team based on reassignment of the incident in Pager Duty? If so, are there any best practices on how to accomplish this?

Has anyone faced similar issue while updating sound over ios app 

We use okta login, I have a Pixel 6 running latest android and latest pagerduty app. The app has developed an annoying bug.When I open an incident to view the details, at the bottom is the function buttons, with Ack on the left. If I tap it, nothing happens. I can wait a long time. I have to tap Ack again, and then I get the banner appear briefly saying the incident was ack’d. And the the button changes to Snooze.I have asked colleagues who have iphones if this is the same for them, and it isn’t. Anybody else got this problem. I tried searching, but the search function uses boolean OR for multiple keywords and is thus relatively useless!I would have added the tag “android” but it’s not possible. hmmph.

Hi all 👋We’d like to set up a way to automatically get notified (ideally in Slack) whenever someone comes on or goes off an on-call schedule.Basically, every time there's a change in who's currently on-call — whether due to a rotation or a manual override — we want that info sent to a Slack channel in a nice, readable format.From what I can tell, PagerDuty doesn’t support webhooks for schedule changes directly — only incidents/escalations. Is there a recommended way to do this? Maybe through the API or another workaround?Appreciate any help or suggestions!

We’ve recently upgraded to the newest version of the PagerDuty integration in ServiceNow.Now what we are finding is that sometime, the priority is not added to the ServiceNow incident that is raised. Most of the time things work fine. But sometimes, an incident is created with no priority.Most days we get one or two. Some days we get 50+.I can see no pattern to what’s going on. Times are random. Counts appear random, and most of the time it works fine.I’ve enabled debugging on PagerDuty, even added a few logs in myself, but I’m not able to see any actually issues.Has anyone come across this? Does anyone have an ideas on how I might move things forward?

HI there,We have  PagerDuty/ServiceNow integration set up with the ServiceNow (v5.0) extension. Over the last week, the extension has stopped working for a particular Service (all the other Services work as expected).I’ve checked and can not find any logging where we can see the extension triggering when in Incident is created (i.e. creating a Ticket in S/N).I’ve checked the UI, and looked though the logging API (`/incidents/{id}/log_entries`), and can’t see if the incident logs the usage of the extension when it triggers?Any thoughts, or help on this?Regards,Dave.

Hi,Rundeck is a great productunfortunately we (and several ppl at guthub, pls see issues) have massiv problems mit jsch until the update to 5.10. Plugins binded with jsch are not working anymore.It would be great to look into this bug, a lot of administrators would be happy again :)Best regardsMarinhioservice.log[2025-04-10T09:06:50,868] ERROR api.workflowstatus - Step 1 failed: git-clone-step[2025-04-10T09:06:51,369] ERROR services.ExecutionUtilService - Execution failed: 7240 in project ABC: [Workflow result: , step failures: {1=PluginFailed: com/jcraft/jsch/JSchException}, status: failed]rundeck.log[2025-04-10T09:06:50,868] ERROR api.workflowstatus [pool-16-thread-1] - Step 1 failed: git-clone-step[2025-04-10T09:06:51,369] ERROR services.ExecutionUtilService [quartzScheduler_Worker-1] - Execution failed: 7240 in project ABC: [Workflow result: , step failures: {1=PluginFailed: com/jcraft/jsch/JSchException}, status: failed]

Does the PagerDuty Status Page automatically show the wrench next to the Services that is scheduled for maintenance based on the time that it is scheduled or do you have to manually push it to in progress? 

Looking to use the API to determine who is on-call and the mandatory field is simply ‘id’. The description of the field is incredibly vague. id (string)                  requiredThe ID of the resource.Where do I find this ‘id’ field? I have tried the URL ID from the service, policy & escalation policy id’s but nothing is working. 

I’ve set up an external status page and checked the box to automatically post incidents to the status page. However, no incidents are showing up. How do I solve this issue?

Hi! What is the expected paging behavior when you add additional responders to an incident?  My team tested adding additional responders to an incident and found that the additional responders kept getting paged after the incident was marked resolved, and they kept getting paged until they accepted the additional responders request. Is this the expected behavior?   My team is interested in paging additional responders until they accept the additional responders request (even if the page is acknowledged or resolved), but I want to get clarity on the expected behavior before we start relying on this feature. 

We have a lot of services for our organisation. If I call the URL https://api.pagerduty.com/services?limit=100&time_zone=UTC then there are too many and the list is truncated. I have tried thishttps://api.pagerduty.com/services?limit=100&time_zone=UTC&name=*E*and thishttps://api.pagerduty.com/services?limit=100&time_zone=UTC&name=.*E.*but they doesn’t work.This seems like an obvious feature to have, but I do not see it in the reference guide, e.g https://developer.pagerduty.com/api-reference/e960cca205c0f-list-servicesis my only choice to iterate through all the pages and pass the output jq, then grep?  

My Rundeck is upgraded to 5.10.  Running on RHEL 9OpenJDK 11.0.25 has a vulnerability and needs to be upgraded.  RHEL stopped support for 11 at .25 so upgraded to 17 and changed the default to 17 which Rundeck shows using 17.I removed OpenJDK 11 from the system but java-11-openjdk-headless remains.  When trying to remove that it wants to remove dependent package … Rundeck.This is a headless install… anyone know how to get Rundeck to move to Java-17-openjdk-headless so I can remove 11?

Isn’t it possible to customize the content of the event text that is sent to a Slack channel ?eg . change the wording, .f.ex add some freestyle text

We implemented PagerDuty Advance in our Slack environment.   It has been a great for our incident channels.   As a manager, the ability to get a quick summarization of an incident is great.    However one side-effect of turning it on, is that we are now getting a lot of noise to our Status/Alert channel.   When an alert is triggered, PagerDuty Advance is adding a bunch of new information into this Slack channel which is not needed within the Status channel.     Before PagerDuty Advance we would get the basic info to the channel (Alert name, Service, Meeting URL)After PagerDuty Advance we now get the above + “What Happened” (useless at time of alert for us) and “Suggested Investigation Path” (also not very helpful for us at the time of the alert)At times this extra information becomes very verbose and clogs up our Status channel.   But I haven’t figured out how to turn this off without turning off PagerDuty Advance.    Anyone have a solution?

Hi there! We have an integration with pagerduty that uses Classic User oAuth. We currently pass the “read” scope. When I try to pass the “write” scope it doesn’t take it. I can create an app with Classic User oAuth manually in the UI but somehow not through the workflow. We use the github.com/PagerDuty/go-pagerduty library for this.It currently calls the following URL: https://app.pagerduty.com/oauth/authorize?client_id=XYZ&response_type=code&redirect_uri=https://abc.com/callback&state=ABC&access_type=offline&prompt=consent&scope=read  If I change it to the following URL it just shows User ID. I would expect it to show write scope in there.https://app.pagerduty.com/oauth/authorize?client_id=XYZ&response_type=code&redirect_uri=https://abc.com/callback&state=ABC&access_type=offline&prompt=consent&scope=writeI also tried using https://identity.pagerduty.com/oauth/authorize URL but no luck. 

Hello, I am interested in knowing does GitLab Changes Integration support  Deployment events, it does work with Merge request event out of the box, will it work with the Deployment events as well ?Thank you

I'm encountering an issue with the PagerDuty integration in ServiceNow and could use some help understanding the error and its causes.Context: In some cases, when a ServiceNow incident is created and we expect a linked PagerDuty ticket to be opened, the PagerDuty integration gives an error that appears in the work activity of the ServiceNow incident: "PagerDuty REST failed to trigger an incident: Service not found".In ServiceNow, teams (Assignment Groups) have associated Business Services where the team is listed as the Technical Support Group. These associated Business Services do not appear to be linked directly to PagerDuty and do not have corresponding PagerDuty services.It may be a coincidence, but it appears that the error occurs when a ServiceNow incident is created with a Business Service for which the Assignment Group is not the Technical Support Group in ServiceNow.Question: Can anyone explain what might be causing this error and how the flow and connections between ServiceNo

Hi PagerDuty Community,I'm currently working on integrating ServiceNow with PagerDuty using the REST API. While testing the incident update (status change to "acknowledged") via Postman, I'm encountering the following error response:My API details and headers are correct. I used the same call from the PagerDuty REST Explorer; there, the integration is working fine.{ "error": { "errors": [ "Incident error illegitimate_requester_error" ], "code": 2001, "message": "Invalid Input Provided" } }