Ask a product question

Hi team, When I run a workflow with an action to add responder on a incident, it is creating so many worknotes on Servicenow. Worknotes creation wont stop until I resolve the snow incident. Could someone help me on this?

Hey, I am using the schedule API https://api.pagerduty.com/schedules/{id} to update the schedule of the specific ID to update the existing configuration layer with new users. But the problem I am facing is, API wont replace the existing configuration layer with new users instead it is adding one more configuration layer with same name. Duplicate configuration layers are getting created. Please help me to resolve this issue.

Hi, We are planning to implement Content Based Grouping using two fields. Upon review, one of the fields is empty for most of the events. How grouping will work based on this scenario? Will it group considering only one field? or Will it ignore grouping since one of the fields is null? Thanks

We are looking to clean up our PagerDuty architecture. We currently have the pattern of “High Urgency” service(s) for immediate notification and “Low Urgency” services for those incidents that should be addressed during work hours, but otherwise get assigned to a dummy user until the next day. Ideally we would like just the one Service where all alerts gets routed to. Then to and escalate based on event severity. We have 24/7 support cover for High Urgency incidents, but we don’t want low urgency incidents going to the on call person over the weekend, evening etc. Is there any way to achieve this? e.g. a) During working hours (08:30am - 05:00pm Mon - Thurs): Notify the on-call person, regardless of severity (HIGH severity is immediate - a phone call, LOW severity can be email) b) Outside of working hours: i) If the alert has LOW severity: Assign to a dummy user. Reassign to the on-call person on the team when working hours start ii) If the alert has HIG

Hi All, I’m trying to revamp our on call schedule and I’m having a hard time figuring out exactly how to configure the schedule / escalation policies to get the desired outcome. We have an escalation policy with 2 schedules on it, a primary and a secondary. When an incident occurs PG pages the primary on call schedule and it that person don’t respond in a set amount of time we have PG page the secondary. At the end of the week the primary engineer rolls off, the secondary becomes the new primary, and the next engineer in the schedule becomes the secondary. It’s pretty straight forward. The desired outcome here is for us to have the two schedules alternate between teams. So if a member of team A is the current primary oncall then a member of team B is the secondary oncall and vice versa. The issue is that our teams are not the same size. This means I can’t just simply alternate the users in the schedule because eventually I would end up with the same team

Hey, I’m trying to create the following: resource “pagerduty_event_orchestration_router” “router” { event_orchestration = pagerduty_event_orchestration.devops.id set { id = “start” rule { label = “Events relating to Ace” condition { expression = “event.summary matches part ‘ace\\b’” } actions { route_to = pagerduty_service.ace.id } } } catch_all { actions { route_to = “unrouted” } } } And getting the following error code when running terraform apply: Error: PUT API call to https://api.pagerduty.com/event_orchestrations/6fd1056d-59f8-4e04-9d90-5d92b1cf301d/router failed 400 Bad Request. Code: 0, Errors: map[sets:[map[rules:[map[conditions:[map[expression:[unexpected word '‘ace’ on line 1 offset 27 unexpected

Hello, Is it possible to send a custom email with Zoom Meeting link and slack channel link from PagerDuty automatically using an API?

Hey all, Pretty new to PagerDuty Process Automation/Rundeck, and have hopefully a general question. Are node filters only viewable/usable by the user who creates them? Is there any way to set these filters at a project level? I’ve created a project for a team to use, and created filters within the node list to group their clusters. We pull nodes from Chef, and their clustering is NOT included in the tags, so the best option I could think of is the filters. Can I share my filters at the project level, or would all the users have to recreate the filters? Or am I dumb and should be doing this another way? Haha. Thanks!

I have an integration where some events sent from DataDog to PagerDuty are being sent as severity “error” when in reality they are just “warning”. (This is due to not being able to set a warning threshold only on the DataDog side.) Within PagerDuty I would like to reset the severity to warning using event rules. Looking at the docs, I should be able to update any CEF field, but severity isn’t in the drop down. https://support.pagerduty.com/docs/rulesets#dynamic-field-enrichment--extraction Can this be accomplished?

Is it possible to customize the email notifications automatically sent by PagerDuty when a incident is created?

Can we select the status update template while adding send status update as an action in the response play?

I recently inherited the my groups PagerDuty. The way my org has this set up is if an email is sent to a mailbox, it forwards to PagerDuty. We have email spam filtering on, and it works quite well in Outlook, however the mail will come in, move the email to junk, and still forward the spam to PagerDuty, thus alerting us. Any help or thoughts would be appreciated.

Hi, I am fetching Incidents information using https://developer.pagerduty.com/api-reference/9d0b4b12e36f9-list-incidents API. Here i am able to fetch all Incidents which are in resolved, acknowledged and triggered state. If i filter user in user_ids[] parameter, it gives Incidents which are in triggered state. Expected behaviour: All Incidents should list irrespective of Incidents status (resolved or acknowledged or triggered) after filtering with user id (passing user id in parameter user_ids[]) Witnessed behaviour: Incidents listed for the filtered user with only triggered state

We have a requirement where in multiple responders from different teams have to ACK an incident. Is there a way for all responders to get notifications until they have ACK the incident. Currently the notifications are paused as soon as one of the responder ACK the incident.

Per the migration guide https://support.pagerduty.com/docs/slack-integration-guide#migrate-to-slack-v2-next-generation - there’s should be a banner with a widget to complete the migration. I don’t see a banner on my Slack Integration page, are the docs outdated or can I validate the version we have somewhere in the UI?

For some reason I’m not able to add the Elastic Alerts integration via the API, it keeps tellng me “Vendor not found”. Here’s my original post request: curl --request POST \\ --url https://api.pagerduty.com/services/<my service id>/integrations \\ --header 'Accept: application/vnd.pagerduty+json;version=2' \\ --header 'Authorization: Token token=<my api token>' \\ --header 'Content-Type: application/json' \\ --data '{ "integration": { "type": "events_api", "name": "Elastic Alerts", "service": { "id": "<my service id>", "type": "service_reference" }, "vendor": { "type": "vendor_reference", "id": "NT0MJYN" } } }' This gave me the vendor not found error and I actually used ChatGPT to get that vendor ID for Elastic Alerts. The reason why I resorted to ChatGPT (Which still didn’t work) is because running this command to get the vendor ID also returned “vendor nout found” curl --request GET \\

Hello, I am working on creating Maintenance Windows through the PagerDuty API. It seems very straight forward but I am not getting past this error: "error": { "message": "Invalid Input Provided", "code": 2001, "errors": [ "Start time cannot be empty." ] } } My request body looks like this, and is exactly formatted like in the API documentation. I’ve double checked the time format, still no success. I guess it’s a super small/simple detail that I am overseeing… { “maintenance_window”: { “type”: “maintenance_window”, “start_time”: “2023-02-17T20:00:00+01:00”, “end_time”: “2023-02-17T22:00:00+01:00”, “description”: “Test Maintenance Window”, “services”: [ { “id”:“XXXXXXX”, “type”:“service_reference” } ] } } Any help is greatly appreciated =) Thanks and regards Daniel

Hi, We planning to enable Content Based grouping. To analyse the data, We need past 6 months of Alert Details ( From the Document, I can see APIs for Incident Report, and Alert for one Incident). Is there any way to extract only Alerts and its fields? Thanks Vignesh, S

I have a team in my org that uses a single level escalation policy to alert all of their responders. They do this because they are responding to critical alerts that have been escalated by upper level executives and they feel that response time is the most important metric for their team. Unfortunately because of this focus on response time, they have responders duplicating work by acknowledging and working incidents that have already been assigned. This team is requesting that incidents only allow a single responder for their incidents. I don’t know that that makes sense, but I think a warning pop up when attempting to acknowledge an incident that has already been acknowledged could work. Maybe make one of these an optional setting at the service level?

For a user is it possible to view all the incidents that were created with that user’s API key? Eg a list of audit events to see what incidents were created with an API key. In the GUI for the API key I see that last usage time is recorded, but can’t see how to get further information via the API.

Hi Team, I want to retrieve the list of incidents from PagerDuty that is less than 2 hrs. duration of MTTR. Looking for solution that can be constructed in browser url. Not the API call. Do we have this feature available to use, if so please guide.

Version 4.10.0 is here! This version includes a faster and easier way to configure the AWS plugin suite. We have simplified how users can authenticate and set up the integration with their AWS account by utilizing the new configuration mechanism launched in version 4.9.0. Read the release notes for more information.

Hello, I am using the /incidents endpoint to sync daily incidents but I’m confused about the responses. For this example I’m trying to get all of the incidents from February 1st. When I request incidents for the date range of Jan 31st - Feb 2nd I get back 64 results, 13 from Feb 1. When I request incidents for the date range of Feb 1st - Feb 2nd I get back 39 results, but missing 2 from the previous request. When I compare the 64 results from Jan31 - Feb2 with the 64 results from combining two individual ranges (Jan31-Feb1 and Feb1-Feb2), they are not the same. Should this be the case? How do I get the full set of the incidents from February 1st? When I requested since=Feb 1 and until=Feb 2, I seem to be missing at least 2 incidents. When I requested the since=Jan 31 and until=Feb 2, I seem to be missing many incidents. Am I using the params wrong? Is this the expected behavior that results from a

With original Global Ruleset functionality, I could adapt content from a certain monitoring tool, transforming its varying severity levels into PagerDuty standard levels. But to conditionally deliver a transformed alert to one of several Services – based on a certain field filter indicating Prod vs NonProd, for example – I had to basically duplicate the original collection of severity-setting rules and combine them with that additional field filter. With Event Orchestration, is there a way to do this kind of “source” adaptation once and feed resulting alert to logic that decides route to Service? Avoiding duplication of transform rules.

Hello! I am new to using PagerDuty and wrapping my head around schedules and escalation policies. We are creating a primary team schedule with two layers. Layer 1 for 9:00 - 21:00 MT and Layer 2 for 21:00 - 9:00 MT. Layer 1 pages folks in the US and Layer 2 pages folks in EU. We are creating a secondary schedule for escalation when primary does not respond after 5 min. For the escalation, I want to tell PD, if person X is paged in primary, then page this specific person from secondary; but if persons A, B, C, or D are paged as primary, then page all of these 3 other people as secondary; but if persons E, F, G, etc. are paged as primary, then page one of these other people as scheduled. Is there a way to set this up or are we forced to say if primary schedule paged, then page secondary, period (i.e., no matter who on primary is paged, the escalation has to be from this one secondary schedule). I feel like what I need should be possib