PagerDuty

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 \\ --url https://api.pagerduty.com/vendors/Elastic \\ --h

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 2 day range would not match the results from those same 2 days when requested individuall

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 possible and I’m missing something obvious like another way

We’ve been experience issues with the PagerDuty Integration with MS Teams since Jan 17, 2023. All of the sudden the incidents stop appearing in the dedicated MS Teams channels. We can create a PagerDuty incident from the MS Team channel which will appear in PagerDuty but if an incident is trigger for any service nothing is created in the MS Teams channel. Also seen 1 out 10 incident actually come through to MS Team channel. We tried removing the PagerDuty app from the MS Teams and disconnected the channels in PagerDuty. After reauthorizing the channels and adding the PagerDuty app to the MS Teams…same results

We are trying to link ServiceNow Business Service with Service in PagerDuty and link it to escalation policy.

Hi, when I’m calling /notes and /status_updates most are successful but they sometimes fail and do not provide a useful error message. When it fails the response code is ‘0’ and the error message is “read ECONNRESET”. I am calling these APIs about 60 times within a minute or two. The same error occurs when I’m calling the APIs separately an hour apart. Most of the requests are successful but there’s a few calls that fails randomly with response code ‘0’. What is causing these errors?

Hello! I haven’t seem any posts for this but I can’t imagine I’m the only person with this requirement. Basically, one of the things we’re using PD for is to trigger on call on support when someone need help off hours. We’re integrating with Jira Cloud and this is feasible. The problem we have is that sometimes we need to request information to further troubleshoot and that is not provided immediately, for the most part. Now, our problem is that we have no way of triggering that incident again when the reply comes. Does anyone have a similar requirement and found a way to workaround it? Thank you!

Here are some further resources for folks looking to improve their automation experience with Rundeck and PagerDuty Automation! Rundeck Rundeck Docs Community Welcome Project (Docker-based) and the tutorial Lunch and Learn: Rundeck and Ansible Ansible Playbooks in Rundeck Intro to Building Plugins in PagerDuty Process Automation On-Prem (PagerDuty Summit 2022) Rundeck Office Hours: Creating a Custom Plugin in Rundeck This is the one with actual code! PagerDuty’s Automated Remediation Ops Guide

Howdy! What is the best way to escalate from one pager duty instance’s escalation to an external contractors pager duty on-call rotation? Idea being that a contractor is responsible for responding to incidents and has their own escalation policies/schedules, and we just want to say the first step on the internal incident is to page the contractors on-call person.

Good day PagerDuty Community, I have a question about Webhook Configuration. I cannot find the answer in the documentation if it’s possible to be informed via webhook when the engineer scheduled a maintenance window and via webhook that the maintenance window started/ended. Is it possible? Best regards, Mariusz Zalewski

Hello Since upgrade Rundeck community to v4.9 I have a problem with WinRM plugin. All Windows Servers are concerned. I have the following error: 1=Dispatch failed on 1 nodes: [xxxxxxx: Unknown: com.dtolabs.rundeck.core.CoreException Do you have an idea. Thanks in advance for your help

Has anyone been successful with ways to mock or stub responses from the API for unit tests? For instance, I have some code that responds differently based on whether they are active maintenance windows or not and I’ll like to be able to test both branches.

Version 4.9.0 is live! This release introduces the beta for Plugin Suite Configuration, which simplifies the configuration of plugins. Read the release notes to learn more. https://docs.rundeck.com/docs/history/4_x/version-4.9.0.html

Hello. I’m creating new Add-on through PD API. Work fine, and I can create some Add-on correctly. Once create an Add-on, I don’t know how I can attach a Service to the new Add-on through PD API. I’ve searched the documentation but can’t find anything about it. Can anybody help me? Thanks in advance.

Context: I am trying to change an existing user role from ‘user’ to ‘observer’ via Update User API: https://developer.pagerduty.com/api-reference/ce6799fc6191a-update-a-user I am able to create new users with the ‘observer’ role via API but in this case I’d like to update an existing user. As the first step I get a user (and it works fine): in user.role = user. Then I change it user.role = observer and call the Update API. Expected behaviour: The role is changed to ‘observer’ and the user is returned with the new role. Witnessed behaviour: It seems the role is not changed as the user is returned with the ‘user’ role via API and shown as ‘Manager’ on the web.

I have a single report of PagerDuty callouts being blocked by nomorobo, which is a “robot smam call management tool used by a number of phone carriers.” PagerDuty may need to take action to get excluded from the nomorobo list. Has anyone else experienced this?