Ask a product question

We are trying to migrate an existing custom event transformer to an App with Event Integration and a custom transformer. The source of the event is an AWS SNS subscription and we are finding that the initial subscription posts are not creating incidents properly. If just using the default/demo transformer, an incident is created but there is no content in the “detail”, so we see no subscribe link. If we change the code at all, we stop getting incidents created at all from the SNS subscribe attempt and no errors with debug enabled. Manual POSTs to the enqueue endpoint using modified code does appear to work, so it’s not clear what is happening to the SNS post. Logged a support case, but haven’t had a response after almost 2 weeks, so trying the community instead.

Hi! In paging software I’ve worked with in the past, I was able to send a page directly to another user, which would alarm on their device until they acknowledged the page (effectively a full test of the paging mechanism). How can I do this with PagerDuty? I tried creating an “Incident” and assigning it to myself, but PagerDuty auto-acknowledges the incident. I tried the “send test feature”, but I only received a ping from this, not an actual page. Thank you for your help!

We have installed and configured the PagerDuty App for Splunk version 4.0.1 and it appears to be working properly. I am a Splunk administrator and have created a test alert that leverages the PagerDuty integration and it works flawlessly. I am able to see the new incident in PagerDuty as well as receive a text on my phone. We have granted a few other teams access to add PagerDuty as a Trigger Action in Splunk Alerts, however when triggered there are no new incidents in PagerDuty and no phone texts. We know that their alert is triggering as they are receiving emails showing that the alert has fired. I checked in the _internal index in Splunk and I see the following error occurs when the alert fires: 04-25-2023 17:06:20.002 +0000 ERROR sendmodalert [2351978 AlertNotifierWorker-0] - action=pagerduty STDERR - splunklib.binding.HTTPError: HTTP 403 Forbidden – You (user=xxxxxxxxxx@costcotravel.com) do not have p

The Current Setup is When PagerDuty is resolved, it resolves ServiceNow Incident as well. What settings do we need to change that not to happen? Requirement is when PD Resolves, it should not resolve ServiceNow Incident. All other bi-directional sync should be same as default. Looking at: In PagerDuty Settings in ServiceNow - Could see that Incident state value to use when PagerDuty resolves an incident field value is se to (6) Resolved which would resolve the Incident in ServiceNow. If I have to change that field value there is no option to select Blank.

Hi, I’m trying to make an API call to reassign an incident while keeping the status as “acknowledged”. I’m using this endpoint with the following request body: { “incident”: { “type”: “incident_reference”, “status”: “acknowledged”, “assignments”: [ { “assignee”: { “id”: “PX****8”, “type”: “user_reference”, “summary”: “User” } } ] } } which successfully acknowledges the user but ignores the assignee field. Instead, the call will assign the incident to the user specified in the from field: { “incident”: { “incident_number”: 60####9, “title”: “Test incident”, “description”: “Test incident”, “created_at”: “2023-06-26T14:09:49Z”, “updated_at”: “2023-06-26T16:24:31Z”, “status”: “acknowledged”, “inci

Hi, Sorry, still new to pagerduty, so excuse if this is trivial… I want to create an escalation policy where the first responder is via an oncall schedule and the second responder is the entire team. But I don’t seem to be able to assign the team to the second notification. The only way is to assign each team member - which means I constantly have to remember to adjust this if people join or leave the team. Thanks for any hints or pointers Mark

I have a use case to notify any existing PD user, ad-hoc triggered from an API. There is no particular on-call. The third party platform triggering the api will provide the user to be notification. Looking for PagerDuty to accept and escalate it

Hello, Simple request How to send a CloudWatch | Eventbridge Event to PagerDuty. Payload are different between a CloudWatch Event and a CloudWatch Alarm. Is there a existing integration that can do that ? Should I rewrite the payload ? Additional info : The events I try to send are EMR errors. https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-manage-cloudwatch-events.html Thank you for your help.

I’ve been googling, reading the documentation and trying different stuff and I can’t find a way to change a service Email integration urgency level to low. RuleSets can do it but they’re about to be phased out and Event Orchestration doesn’t seem to be play nice with email integration. Coming from OpsGenie it feels like PagerDuty is making simple stuff like this simply impossible or overly complicated. And no, we don’t have PagerDuty AIOps package.

Hi, If we enable grouping using any of the available methods (time/content-based/intelligent), Is it possible to modify the subject with the alert count in that incident? for example: Incident with 5 alerts grouped - Subject: [5 Alerts] Orginal Subject or Can we send that alert count to Slack thread? Just want to improve Oncall experience by giving them the alert count in their Slack notification itself. Thanks

Hi there! My name is Martin Stone, and I’m a PagerDuty Solution Architect. I want to share a little side project that I’ve been working on for while, because it’s starting to get pretty useful. It’s a new command line interface (CLI) for PagerDuty. There are lots of ways to interact with PagerDuty programmatically, but I wanted to make something that was user-focused, easy to install, and easy to use for common PagerDuty tasks. Among other things, it’s good at user and admin tasks like “acknowledge and snooze all my incidents,” “put a bunch of services into maintenance mode,” “output a CSV of some or all users,” and so on. It’s super easy to install and get started. My PagerDuty CLI is open source and it’s implemented in TypeScript using the oclif framework. I wrote a user guide that covers installation and gives some examples; you can find that

I have a tool that does not conform to what PagerDuty needs when I send in an event. I also cant modify what this tool is sending to PagerDuty, I can only use the out of the box payload values. Is there a way within PagerDuty to transform the source data (new) to what PagerDuty requires (trigger) and then send the event off for processing? Thanks

Resolving Incident in ServiceNow is not updating PagerDuty Incident Status to resolved. Everything else works except for this. Has anyone else run into this minor issue? Thanks in advance. Edwin

Hi, We are exploring Service Orchestration Rules, Rule 1: If the event has any priority in the custom field then it should set the priority in Pagerduty Incident, We have one nested rule for one priority. Rule 2: If the event has a hostname it should create a new field in the custom details ex: alert_hostname We want all the alerts should pass through both rules. Instead of copying the 2nd rule in all the nested rules, Is there any way to process events in more than 1 rule by default? Thanks

We are using the PagerDuty APIs to get all incidents and single incidents successfully. What we need now is to be able to load CUSTOM DETAILS. I have tried using the include[] query parameter on some requests and have looked at the log entries API as well but still cannot figure out how to load this data? Can you provide a simple working example? I have seen other posts similar, but have not seen a working example yet.

Can someone please help how to fix this. I have sent mail to PD support, but have not got any reply from last 2 weeks.

Hi Everyone, I have been trying to retrieve data using https://api.pagerduty.com/analytics/metrics/incidents/services but I am not getting consistant data. There is mismatch for the data which I am getting on pagerduty to the data retrieved through this API. I am passing the Service Id , Team Id to fetch data for high urgency incidents but there is huge inconsistency compared to actual data in pager duty. Has anyone come across similar situation or have a fix this issue. Thanks

on April 13th we submitted a vulnerability report concerning the handling of private keys in tempory storage, but never received a feedback, even after writing a follow-up. We used the link provided in https://github.com/rundeck/rundeck/security/policy Does pagerduty discard all non-enterprise customer feedback?

Hi there Is there a way to restrict creating technical services in Pagerduty to Global Admins only??

Hello Folks, I have a working GCP PageDuty on-way notification channel which is creating incidents anytime an alarm is triggered. The only issue I’m facing is that when the alarm is resolved automatically when, for example, CPU goes back to normal, the incident in PagerDuty is not being resolved automatically. Is this expected? It would be nice if the incident is resolved automatically when the CPU goes back to normal. Could someone confirm if it is possible to resolved the incidents automatically, please? Thanks, Gustavo

Hi! I’m looking for a way to visualize at the PagerDuty UI all incidents given an incident_key. I know there is a way to get them through the API https://api.pagerduty.com/incidents?incident_key=&time_zone=UTC but is there a place where to visualize all these from the PagerDuty UI?

api_token = “” session = APISession(api_token) for user in session.iter_all(“users”): print(user[“id”], user[“email”], user[“name”]) This code iterts to all the users and provide their id, email and name I want just for specific users can you pls tell how can i. do that

I want to have slack notification to specific channel from PagerDuty who is on call now based on the schedule with different escalation policy levels. How can I implement it?

I’m currently trying to figure out whether I should create an incident through the REST API V2, synchronously or asynchronously. I read here that the REST API V2 is a synchronous API. I was curious if there was any SLA on the maximum amount of time we should expect to get a response back from the incident creation API.

Which integration is better to create an incident dynamically? and Why? Calling PD API from external application program to create an incident Or Sending email message to integrated service email address ( domain@pagerduty.com) to create an incident .