Recently active topics

Based on the Pagerduty documentation, it seems like “description” field is no longer supported and only the “title” can be retrieved via webhook. These two fields are very different, as one is a quick summary and the other provides scope and context necessary to understand an incident. Is there a workaround to retrieve the description field via webhook? This is normally where we would put a paragraph of additional critical context as such as the Slack thread of a user-reported issue, details about the scope of the issue, etc. Does anyone have any advice on what to do?

PagerDuty has an option to “Send a Webhook POST” in an incident workflow. I’m trying to set an automation incident workflow based on a specific custom incident type. My final step is to include the resolution note, but I’m not seeing a way to do this. It sounds like something any average user/customer would want to hear about (e.g. I want to know what the resolution was to the incident), but why is it not available as a field? Or does anyone have a workaround on how to capture it?In the body of this text field, it shows a bunch of incident-related options, including “resolveReason” which to a regular human seems like it would be the same thing as “resolutionNote” but it’s not. It seems to only be used to determine whether it was a merged incident or not. Is anyone in the same situation? I can’t be the only one who wants to query the resolution of an incident so we can send communications around it. This seems like a severe product gap that I’m surprised hasn’t been addressed. I know Pa

Hi!I have setup the Bitbucket integration on one of my services follwing this guide: https://support.pagerduty.com/main/docs/bitbucketHowever no incidents get created ever. Is there anything i have to consider that is not mentioned inside this guide ?Could it fail because Basic Service Event Rules is not activated ? Do i have to configure anything inside the event orchestration rules ?  I literally just did what the guide said..On build updates the webhook is received by pagerduty with HTTP status 202.I also get an event id on response:  The builds i am testing are FAILING builds…Any ideas ?Is the integration deprecated ?

HiI tried to use the PD MCP in VSCODE for auto create Schedule Overides but I’m always getting the error: “Sorry, no response was returned.” My MCP config is below:"io.github.PagerDuty/pagerduty-mcp": {"type": "stdio","command": "uvx","args": ["pagerduty-mcp==0.2.1","--enable-write-tools"], “Get” operations are working fine. My request is: schedule_id: "P76S19G"override_request: {  "start": "2026-02-08T18:00:00+02:00",  "end": "2026-02-09T08:00:00+02:00",  "user": {    "id": "PNBBMSL",    "type": "user_reference"  },  "time_zone": "Asia/Jerusalem"} will appreciate any help here

Just launched a PD on PD section in the Ops Guides that might be useful if you're looking to get more out of PagerDuty (or convincing your team to adopt better practices)!  We documented how we actually use PagerDuty internally at PagerDuty — the good, the bad, and the "oh that's how they do it" moments. There are 10+ real stories covering different use cases, plus a bunch of best practices we've learned in the process.When folks ask us "okay but how do you use it?" — it turns out we have a lot to share that is useful for others trying to level up their incident response game or just looking for ideas.  Feel free to reply with any questions!

We are counting down the days until we see you in person. The PagerDuty On Tour series is moving fast, and we have some massive updates to share with you today:🇦🇺 Sydney & 🇬🇧 London: The lineup just got even better. We’ve officially confirmed a new wave of incredible speakers for both cities! Get ready for deep dives into operational maturity and real-world incident response stories. Check the updated agendas: London | Sydney🇯🇵 Tokyo: Konnichiwa! Our official landing page is LIVE. Head over now to see what we have planned for our Japanese community and secure your spot.🌉 San Francisco: We are targeting Spring for the Bay Area stop. More info on that soon!👇 Choose your City and Register for FREE:https://www.pagerduty.com/on-tour/ 

Hi everyone — Maria here 👋I recently joined PagerDuty as a Community Program Manager and wanted to properly introduce myself.Before joining PD, I spent most of my career designing developer programs across open source, Web3, and space-tech communities. That mostly meant running hackathons, education tracks, and experimentation programs that help devs explore new tools, share feedback, and build cool integrations.PagerDuty’s developer and community ecosystem is still evolving, which honestly makes it a very exciting space to join. B2B developer communities often look very different from open-source ones – devs are usually balancing community engagement with their day jobs, which changes what feels valuable, fun, or realistic to participate in.I’m curious to learn from you:👉 What kinds of developer programs feel genuinely useful or enjoyable to you?👉 What formats feel exciting vs. what feels like extra work?Some examples I’ve worked with before include:• Hackathons• Integration / auto

My organization just recently got a subscription for PagerDuty at the Pro plan level. This has been an uphill battle for me for almost 7 years now to get this as my current leadership believes all alerts and notifications should be via email and should always hit everyone all at once.I came from an organization that used XMatters, so my experience with targeted alerting and triage is there, but it’s not far different in philosophy than PagerDuty. My argument is that we should only be alerting on critical items, and it should be using a workflow and start at the lowest level for triage then escalate as needed after triage. Instead of everyone getting an email all the time, proper incident management should be done where a ticket is also generated in our ITSM tool, then appropriate communications from the ticket go out at regular intervals to stakeholders. One of the arguments I often get is “We’re a small company”, which I disagree with, we solidly fall into the mid-size enterprise, but

Issue Summary:We're experiencing a problem where ServiceNow incidents triggered by Solarwinds alerts are not creating corresponding incidents in PagerDuty, even though they meet the priority criteria (P1–P3).Context: Solarwinds is our alerting tool, integrated with ServiceNow (Yokohama, PD Spoke 1.4.0, PD 8.2.0). ServiceNow is configured to forward P1–P3 incidents to PagerDuty. We're using assignment group services only in PagerDuty (no business/technical services). This issue began after integrating Solarwinds through ServiceNow Event Management. What we've observed: Some PagerDuty webhooks become disabled intermittently, though health checks often return normal. The issue is inconsistent—not all Solarwinds-triggered SNOW incidents fail to generate PD incidents. We suspect a possible problem with the PD Spoke workflow or webhook handling, but haven't confirmed. If anyone has run into a similar issue or has suggestions on what to check next, I’d greatly appreciate your insigh

I have a Pager Duty incident alert rule which is:A valid Service Offering (in ServiceNow) A valid Assignment Group  (in ServiceNow) A P1 or P2 incidentI have had two incidents in the past few weeks where the integration failed with the error:  Error: "triggerIncident response status:400, error:Incident could not be assigned error: undefined". Some incidents in between have created the alert from Service Now to Pager Duty and the Incident Rule ran fine, this morning I had another one.  I would like to understand why this is an intermittant issue before it becomes widespread.Pager Duty has been configured out of the box, no customisations, the same for Service Now and imported the Services, Assignment Groups and users the recommend way (from Service Now via the API/integration).

I have a Pager duty system in which i can add up to 3 phone numbers to get notify about an alert.Now my question, is there any possibility to add n number of phone numbers..?

Hi everyone 👋We use PagerDuty daily at our company, and it’s become a core part of how we run on-call and incident response. One thing we felt was missing, though, was an easy way to visualize key PagerDuty information on a large, always-on screen — for example in a hallway, NOC, or team area.So I ended up building exactly that.I’ve added a PagerDuty integration to my open-source tool RepoSquirrel, which can display things like: Number of open incidents High-level PagerDuty status Other at-a-glance information suitable for kiosk / wallboard use Project repo:https://github.com/reposquirrel/reposquirrelI’ve also written a short page describing the PagerDuty integration and the intended use case:https://github.com/reposquirrel/reposquirrel/blob/main/docs/pagerduty_integration.mdI wanted to share this here in case it’s useful to others, and I’d love any feedback or ideas for improvements. Happy to share screenshots, demos, or implementation details if anyone’s interested.Thanks — and

Hi All! Just had LCR added to my account and set up a number. Upon testing, I’m a bit disappointed so far for the following reasons: The voicemail does not come through on the initial call to the person on call. It would be preferable for the user’s voice message to play directly when acknowedging an incident. The voicemail isn’t super obvious on the incident. It’s a little hyperlink at the bottom and opens in a separate window just to click the little play button. The smartphone app seems completely useless for this feature. It shows the same hyperlink, but will not work unless you are actively logged into PagerDuty via your phone’s web browser. Is this just how it is for LCR right now? Please tell me I’m missing something, because I’m extremely disappointed given the price that LCR costs.