Ask a product question

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

Where can I find exact steps to create an incident using Slack workflows? I’d like our support folks to be able to trigger a pagerduty incident, however they don’t need/have PD licenses and can’t use /pd incident command. Slack integration article link to incident creation seems to be broken: PagerDuty Knowledge Base Slack Integration Guide | PagerDuty Slack + PagerDuty Integration Benefits Incident response capabilities within Sla

Hi All, Do we have documentation or a walkthrough on how you can link a business service to multiple technical services using terraform?

We have incidents that are auto resolved almost instantly after it gets auto created. How do we auto assign priority to these auto resolved incidents because we often miss these auto incidents to assign the priorities manually

Hi there, Couldn’t find an endpoint in API reference to retrieve the json response in the link below, only the link itself. https://company.pagerduty.com/incidents/XXXXXXXXXXXXXX/log_entries/XXXXXXXXXXXXXXXXXXXXXXXXXX Any ideas to get the desired info? Thanks.

On Resolve, I’d like to update a mandatory field in the ServiceNow incident. is inbound field rules the easiest and best way to accomplish this.

Hi, I’m trying to setup a 2 way connection to my sentinel instance from PD. I have set up the connection from Sentinel to PD and I can create incidents with the API. In order to sync back to Sentinel I’m using the webhooks. But I’m having trouble in providing a reference point for Sentinel to understand which Incident needs updating given the HTTP info that PD send to Sentinel. I have two main questions; List item Is there a way to create a custom field, so I can populate it with the Sentinel Incident reference ID? Can that ID be send back to Sentinel in the payload of a webhook?

We had Microsoft Teams configured using the legacy connector through webhooks. I finally have gotten around to trying to update to the new integration and where I am supposed to do @PagerDuty accountLink, it sends me the PM as expected but when I go through the process on the PagerDuty website it ends at a screen with the following. "#### An error has occurred and we are unable to link your accounts at this time. Your team of the Microsoft Teams account is connected to another PagerDuty account." I then attempted @PagerDuty unlink from the channel and got the PM again and that stated the following “This Microsoft Teams user account is not connected to a PagerDuty user account. The UnlinkUser command was cancelled.” So it would seem that PagerDuty sees a linked account with this teams channel but Teams does not see it when it attempts to interact with PagerDuty. I am not a PD admin so when I try to go to Integrations I can not see anything but I as

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.