PagerDuty

I have a schedule defined with two layers, each a week in length. Each of the layers defines a 12 hour shift, one for US based people and the other for India based people. For the US based layer I want to create an override for the entire week that just replaces the US based person and not the India one. In other words, a different person will take the US shift for the entire week, but the India person will remain unchanged. How do I do this without having to schedule an override for each 12 hour shift of the US person?

Hi, I want to delete service routes that are inside an Event Orchestration automatically via Python, but I don’t see any documentation about any endpoint from the API to do it. Can someone give me more feedback about this? Thanks :)

Or how to send incidents for PagerDuty to Discord.Any ideas on what’s the best way?

Users on my company instance have noticed that PagerDuty is behaving differently when an incident is initially assigned to a team/service vs when a responder uses the “add responder” feature. Normally when an incident is ack-ed or resolved, further notifications are suspended or terminated. However, our major incident has begun engaging other teams by adding responders to existing incidents recently and it seems to work differently.Users are reporting that they are getting notifications even after the incident has been resolved. Additionally, when there is more than one responder on a given escalation policy rule/level when one user acks the alert, that does not prevent other users from continuing to get notifications. Another difference is that the notification times and methods for each user contacted are not logged in the incident. This last bit was especially confusing for the users when we were first investigating this issue.Is there a reason for this difference? It’s not intuitiv

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

Hi All!  I’m using Email Integration with my Service.  I configured a Trigger Rule with a Custom Field - severity that I derived from the email body.  I want to reference that Custom Field in a subsequent Service Event Orchestration Rule, which would be called  event.custom_details.severity and be referenced within the Rule Condition as If event.custom_details.severity matches info.  This condition isn’t firing, and yet when I see the Incident info (via Fallback Behavior), I can see my custom field severity with a value of info under the heading DETAILS. Should I be able to reference this custom field, and if so, how can I do that?  Thx!  :-)

Hi Experts, I have a Terraform setup which runs github actions and everytime, either the Terraform Plan or Apply runs, during the refresh of the integrations it keeps giving timeoutError: timeout while waiting for state to become 'success' (timeout: 2m0s)Error: Terraform exited with code 1.Error: Process completed with exit code 1.Any help would be appreciatedRegardsRaheel

Hello there, Has anybody had success with setting up the integration between ninjaOne and PagerDuty? ninjaOne has an option, but PagerDuty does not have any option for ninja. Thank you!

I have deployed rundeck 5.7.0 war in a UBI8 container. I am getting the below error while creating the project.  

We have 7 team members, I want to create oncall schedule in Pager duty with below scenario 9 AM - 4 PM (Monday - Friday) single person rotation everyday 4 PM - 2 AM (Monday - Sunday) single person rotation (weekly basis) so one person will be doing monday - friday But the person oncall fr the week from 4 - 2 AM cannot be part of 9 - 4 PM How can I set this oncall schedule. tried with two layer but it overlaps for few ocassion

I’m trying to use Runbook Automation to run SQL against Google BQ tables on different projects to determine what the next action should be for resolution. To query as a specific service account, I need to pass a file from the keystore, but I’m having difficulty accessing it from either a Bash script or an Option. Is there a paved path for plan for having a standard workflow step for running SQL against GCP BQ?

How can I setup okta with rundeck community

Hi, I want my team to be on call 3 days at a time, with no weekends. This doesn’t seem to be possible, when I add the restriction of Monday to Friday, the scheduling of the 3 days for each person still runs into the weekend.I even tried to add another layer with just one person on it at weekends to try and block these days out, but it still doesn’t work.You can see in the image for example 6th December, Jake comes on the rota for only half a day, because the schedule is still running him through the weekend, even though weekends are excluded.It should be (from the start)David - Monday Tuesday WednesdayJake - Thursday Friday MondayMark - Tuesday Wednesday ThursdayGerald - Friday Monday Tuesdayetc. Surely this is a relatively common requirement - there must be a way I can do it? What restrictions do I need to set? Any help would be appreciated!Thanks,Davidcurrent restriction config 

Hi team,My company manages PagerDuty configuration in terraform. One resource we manage is a PD Slack connection. From this doc, it mentions this resource requires a `user_token` API key. https://registry.terraform.io/providers/PagerDuty/pagerduty/latest/docs/resources/slack_connection My question is, what happens when the user leaves the company? Will the user API key become unusable?

does anyone aware of the audit or report that we call pull where the person is on call but never recevied a notification ?

The attached screenshot is taken from an incident in the PagerDuty web UI. I’ve recently updated the associated service not to auto-resolve incidents, but how can I change an existing incident, which has a pending action, not to take that action?I've tried to set the set the incident’s “pending_actions” field to null or [] via the API, but the change didn’t take effect. I also don't see any button on the UI for this. Is there a way to do it?

Hello, I am new here and looking for some help/direction.What: our company uses Teams and I want to give our support staff a button in our SEV-1 channel that they can push that will page out for on-call staff to attend the triage call.Why: we are seeking a “faster than calling the support number” means to initiate incident response.for customer reported issuesIs there a simple way to achieve this? 

I have a rotation I’m scheduling for with two employees that work different hours. Employee 1 works 8a - 5p M-F Employee 2 works 3a - 12p M-F I’d like to rotate between the two employees on a weekly basis. I’m basically trying to do follow the sun, but with alternating weeks. When no one is available from this level, it will go to the regular on call rotation schedule that already exists. Is this possible? I’ve poked around the documentation a ton and the only way I’ve been able to accomplish this is with manual overrides.

 Hello everyone,I am facing a challenge with setting up alert routing for Kubernetes clusters using Prometheus and PagerDuty, and I wanted to seek your advice or suggestions on how to solve this. ### Problem:We are currently using Prometheus rules to trigger alerts and send them to PagerDuty (PD) for our Kubernetes clusters. At the moment, all our alerts are routed to a single PagerDuty service. Now, we need to separate these alerts based on labels in the Prometheus rules to ensure they are handled by different teams. Specifically:- We want to route alerts for different teams based on labels defined in the Prometheus alerting rules.- Each team should have its own escalation policy within PagerDuty, but we must keep using a single PagerDuty service.- Unfortunately, we can't use the **AI Ops feature of PagerDuty** to help with this segregation. ### Example:We have two teams, **Team A** and **Team B**. Alerts for these teams should be routed based on a label in the Prometheus alert rules.

Hello! I am a new user of PagerDuty (my division just signed me up). Using PagerDuty, I would like to create a workflow that would allow me to incorporate automation as part of my escalation policy. For example, I would like an escalation policy to… Notify me that there is an error Kick off a script that will generate reports / automation Depending on the response in step 2, provide me another tailored notification Does PagerDuty support this?

Our use case seems to be the opposite of what PagerDuty currently supports.   I know we can use the Dedup Key to merge alerts into an already open incident and help with grouping alerts.     However our use case is to not send a notification unless we have received X number of alerts in Y time.       What we see is that a run will fail, but the next run in 15 mins is successful, so our on-call person is getting paged and then resolving the ticket because the next run was successful.    Would be good to not page the On-call person unless the next run also fails.    But haven’t seen how to handle this in PD.  The Auto-Resolve doesn’t work in our case because they are individual alerts - from seperate runs of a pipeline - the dedup key is what links them. Has anyone dealt with a use case like this?   Have you been able to solve it?

We have a use case that looks to not be supported by PagerDuty, wondering if anyone has a way to implement this scenario.Our pipelines are dependent on 3rd party APIs.    When there is schedule maintenance of an API, we would like to be able to disable all alerts related to pipelines that are dependent on that API.     I have looked into setting up the API as a dependent service, but it doesn’t look like I can do anything with this linkage to suppress alerts.   

We have upgraded to Webhook3 and have all intergrations intact howevee still we have observed duplicate incidents created by PD in SNOW. Please advise if this is known issue.

Hi there, new around here with a quick question. I’m trying to set up automation so as on-call changes week by week it can automatically update a Slack workspaces @oncall-team alias. IE: Person A and Person B. Week 1 Person A is on call the @oncall-team maps to Person A. Week 2, Person B becomes oncall and @oncall-team alias automatically updates to Person B. Any tips? ChatGPT didn’t bring up anything fruitful.

Occasionally we’ll see false alarms in PagerDuty due to an upstream issue coming from Splunk or New Relic. These are alerts that fired due to testing, maintenance, or some other event that we don’t want to “count” as real production incidents. I don’t see an ability in the tool to archive/hide/etc. these events so that they don’t clutter up our reporting & analytics.  Anyone else have a solution or approach to manage these?