Ask a product question

Hi, We have been exploring various reporting options, and it seems that we have encountered a slight limitation with our current capabilities. We are interested in creating a report or knowledge base that would allow us to search for an Incident name and retrieve all associated notes from incidents with the same title. Currently, our incident titles are based on AWS alarm names that arrive to PagerDuty. We would like to know if it is possible to generate a report that includes the notes added to PagerDuty for each AWS alarm (In essence, it would refer to a single Incident name and encompass all the notes that were added to multiple Incidents sharing the same name). Is this a feature that is supported within the PagerDuty workflow?

Hi, I am currently facing a challenge with managing AWS events through PagerDuty. Our objective is to automatically merge multiple identical events into a single incident and suppress all subsequent notifications. Unfortunately, we have encountered difficulties with the “Content-based” option for noise reduction in the Service Settings. Although different events were merged into a single incident, they were not actually identical. We attempted to solve this issue by using Event orchestration, where we set up a process to match the desired line in the ‘event.summary’ and then suppress multiple occurrences of these events using nested rules. However, this approach did not yield the desired results. I would like to ask if using Service Alert Grouping in combination with Event Orchestration is a normal practice, or if the Orchestration can “overwrite” the Service Alert Grouping settings. Would you be able to guide me to identify any flaws in my thinking or documentation that

Is this intentional? I just scheduled several overrides, but none seem to have any effect whatsoever on my Google calendar. It shows the regular cadence, meaning ones I’ve had overridden are still there and overrides I’m taking are not. This unfortunately renders the feed pretty much useless for me. The URL is still the same and I’ve refreshed the page several times. Am I missing something?

We are looking to integrate Dynatrace with Pagerduty. We are employing the out-of-the-box option that is mentioned here - Create an Integration on a PagerDuty Service I am looking for references about ‘encryption-in-transit’ AND ‘secure authentication’ between the two SAAS product. Please could you help with any reference material (video, demo or document). Much appreciate this! Regards, Amith

Hi, From my understanding there is no way to list incidents for an specific service which have been “Suppressed”, or that are an “Anomaly”, on the Online interface. See attached screenshot. Thus, I started looking into the API, and although I can list incidents for an specific service, I can’t seem to find a way to query based on the Incident Type: “Frequent” “Rare” or “Anomaly”, or if they are: Urgency: “Suppressed” or Status: “Resolved (Suppressed)”. Does someone know if this is possible?

I am using Service orchestration to Route incidents to different Services and want to define Custom Variable from source (default Pagerduty source) and replace CEF fields class, group and component using Regex RE2 (?i)(\\W|^)(credit)(\\W|$) I am not getting event fields replaced here. Any reason. I am not using AIOps Pagerduty. Source: raw_event.summary and event.summary

Hi, https://developer.pagerduty.com/api-reference/f3bfe4c8d1de2-list-the-supporting-business-services-for-the-given-business-service-id-sorted-by-impacted-status gives us a list of business services and their supporting services. How can we set supporting services for a business service via the API? This endpoint: https://developer.pagerduty.com/api-reference/3fb4a13b59634-associate-service-dependencies seems to only work for technical services, not for business services Thanks!

Hi all. I’m wondering if the REST API has a default filter for the list incidents endpoint. I created a few test incidents in the website a few months ago and they were showing up before in the API but now they are not there any more. I then proceeded to create a new Incident and that one is present in the API response though. Is there some sort of filter being applied so that only incidents with a certain age are being sent? What else could be the cause for this behavior? This is the full URL I’m using: https://api.pagerduty.com/incidents?include%5B%5D=assignees&limit=200&include%5B%5D=first_trigger_log_entries

Hi, I am fairly new to PagerDuty, and I am working on a task to fetch data from PagerDuty and load it in a bucket in GCS and I am planning to do it by a Python script. Can someone please give me a high level overview of how to do it? I am not sure if I should use Rest APIs or Event APIs. Any guidance would be much appreciated, thank you!

Hello community, greetings from Brazilian countryside! I’d like to know if there is any chance to change my mobile device name. Today we use one login to 4 users, and for our iPhone users we’ve gotten a problem. The device name is the same, and I couldn’t find where do I change the device name, e.g. Lucas’s iPhone, Mark’s iPhone, etc. Is there a place to do this change? My best regard! Lucas

I am following this api doc, creating tech service document, using python/requests. After a few tries, isolated the problem to incident_urgency_rule first try, using all default values in sample code, all good "incident_urgency_rule": { "type": "use_support_hours", "during_support_hours": { "type": "constant", "urgency": "high" }, "outside_support_hours": { "type": "constant", "urgency": "low" } }, second try, simply change outside_support_hours / urgency value to high, it gives me 400 error. "incident_urgency_rule": { "type": "use_support_hours", "during_support_hours": { "type": "constant", "urgency": "high" }, "outside_support_hours": { "type": "co

We have a service setup that uses an email integration. We’d like to suppress incidents/alerts during our business hours. Under settings for the server we have setup a service event orchestration. It’s setup for a weekly schedule from 8:00 AM - 5:00 PM M-F to Suppress incidents and notifications. This seems exactly what we want, but the incidents still get generated. What are we doing wrong? Thank you

I get different results that I do not understand depending on how I call the api endpoint. incidents_endpoint = url + f’/incidents?limit=20000’ -> 14 incidents incidents_endpoint = url + f’/incidents?date_range=all’ -> 9 incidents, different than the first 14 incdents_enpoint = url + f’/incidents?date_range=all&limit=2000’ -> 100 incidents How can I get all the incidents? (I have over 300, can’t ever seem to get more than 100). Is there some pagination? How does that work?

Hi Can anyone please tell me how I can limit the rights an API key and request has? Have a rather urgent requirement to give out a key but I’m not sure how to restrict what the API request can read and write. The team in question need to write incidents to their own service. Many thanks

Hey there, We’re working on moving to zabbix from an old legacy monitoring system, and one thing that was essential for us was having Acknowledgements in PagerDuty show up in the monitoring system. So we wrote it: https://github.com/sonic-com/pagerduty2zabbix Handles: PD incident ack -> zabbix event ack PD incident un-ack -> zabbix event un-ack PD trigger (creation) -> zabbix comment of link to the incident in PD PD incident note -> zabbix event comment PD incident resolved -> zabbix event close attempt PD incident priority update -> zabbix event severityupdate Anybody want to help test it out? Caveat: not designed for super high alert volumes (it’s a perl CGI). Also, in my testing it only works if the PD integration is the generic “events api v2”; the “zabbix”

We are building Zabbix v6 with Ansible on Linux, integrating PD in the Zabbix alerting. The RPM package pdagent is failing to validate the GPG signature. Giving this error: Signature not supported. Hash algorithm SHA1 not available .\\r\\n\\r\\n{“failed”: true, “msg”: “Failed to validate GPG signature for pdagent-1.7.3-1.noarch” The Ask: Is there a more recent key for GPG signature available for this package? Signing with SHA1 algorthm is deprecated…right?

Some spark notes and biz value from this release. Runner secrets authentication improvements Last release we announced support for integrating Runners with secrets-management providers that could be used in Job Step plugins. Now, the keys retrieved from this integration can be used with Node Executor and File Copier plugins as the method for connecting with remote nodes. The Runner can retrieve those secrets from providers like Vault and connect and execute commands or scripts on nodes. Runner Key Storage enhancement Previously, if a Runner was integrated with a secrets-management provider, then a Job executed through that Runner couldn’t use secrets stored in the native Key Storage. With this release, that limitation is no longer in place. Now the Job can use both the Runner (and Key retrieved through the Runner), as well as keys stored in the native Key Storage facility. Cross-role and cross-account support for EC2, AWS Systems Manager

Hi there, We are currently running v7.5 PagerDuty ServiceNow app. However, we have a mix of V4 and V7 of services under service directory. I was told to run the “Migrate Webhook to 7.5” script in Service is in order to upgrade those V4 services. Has anyone done it before? Is there any risk on messing up what is already working? Seems like it’s just clicking on a button in ServiceNow…. But wanted to make sure I am not breaking anything… Thanks

Hello everyone! I’m looking for a piece of advice, got stuck with integration between PagerDuty and Google Cloud Monitoring. In my GCP project, I have several alert policies that trigger when cloud function execution fails. After a policy is triggered an incident in GCP is created and after some time it gets resolved if a condition doesn’t meet. So it works fine. We recently started working on an infrastructure monitoring project and have been trying to integrate those cloud function incidents into PagerDuty. By enabling PagerDuty Services on the GCP side we managed to perform a basic integration and new incidents are now successfully forwarded to PagerDuty. But all subsequent changes in Google incidents are not displayed in PagerDuty, neither acknowledging nor closing. Such behavior creates a lot of noise on the PageDuty side because effectively closed incidents remain open in PagerDuty and we have to resolve them manually. On the Goggle side

Good morning: Have a user that is receiving a banner about having 3 onboarding goals yet when they click the “See Goals” button there is nothing displayed for them to do. Is there a way to clear this or see what is needed to complete the goals? Thanks, Eric .

Want to send the suppressed alerts only via email and not via phone call to the on-call user? So that the user does not receive call during off-hours and can work on suppressed alerts on next day.

I’m configuring a service with an email integration and testing it. As per documentation it says that Open a new incident/alert for each new trigger email subject (default): Emails with the same subject line will deduplicate. For example, if PagerDuty triggers an incident in response to an email with the subject “Host Down”, subsequent emails with the same subject will not trigger a new incident. Rather, the new email will be appended to the existing incident’s timeline. I’m trying the same, so when email comes with same subject it should create only one incident and following emails should append the existing incident. But the following emails are not appended to the existing incident, which is causing me to loose those alerts. How can i get the alerts appended to the original incident without loosing it. Please find the setting below

We are seeing incidents raised with name “unknown rule” without any proper info of incident. Does anyone know the cause. The integration it is coming from is Microsoft OMS

Hi, I created an Event API V2 integration and test it with the CURL provided. But I did not get an incident on the Open incident page. Below is the test crul and response. Note: i removed the integration key from the curl commends. Thaks. Bill. curl --request ‘POST’ –url ‘https://events.pagerduty.com/v2/enqueue’ –header ‘Content-Type: application/json’ –data ‘{ “payload”: { “summary”: “Test alert”, “severity”: “critical”, “source”: “Alert source” }, “routing_key”: “”, “event_action”: “trigger” }’ {“dedup_key”:“a4c4fcd0e2da490eb2791920699eaee0”,“message”:“Event processed”,“status”:“success”}bash-5.1$

Critical Alerts for iOS allow push notifications to bypass an iPhone’s Do Not Disturb and silent mode settings, But I can’t find this setting in my app, the system is ios 17.0.1