Recently active topics

🇬🇧 👋 PagerDuty On Tour London: Who’s here? Let’s connect!

PD On Tour is taking over London today with an agenda packed with insights on the path to autonomous operations, and I know many of us are looking forward to seeing how AI and human expertise are coming together to reshape our work.Let’s get this conversation started here! Reply below and introduce yourself:Who are you? (Name, Role, Company) What is your "one thing"? What is the #1 topic or feature you are most excited to hear/learn about today? What’s the most interesting thing you’ve learned so far? Can’t wait to meet you all in the comments (and in-person around Convene throughout the day)!

700

3 days ago

PagerDuty Community TeamCommunity Manager 💚

[Workshop] Golden Paths to Production: Build a Self‑Serve, Zero‑Toil Platform

We hope you enjoyed the PD On Tour London workshop Golden Paths to Production: Build a Self‑Serve, Zero‑Toil Platform session, led by Justyn Roberts. Let’s keep the conversation going right here!👇 Comment below with:Any burning questions you didn't get to ask Feedback on the session (what did you love? what do you want more of?) Any cool resources, links, or tools mentioned during the workshop.Can’t wait to see what you all took away from it!

340

PagerDuty Community TeamCommunity Manager 💚

[Workshop] AIOps Revolution Bootcamp: From Reactive to Proactive Incident Management

Attending PD On Tour London’s workshop AIOps Revolution Bootcamp: From Reactive to Proactive Incident Management session, led by Cristina Gonçalves? Let’s keep the conversation going right here!👇 Comment below with:Any burning questions you would like to ask Feedback on the session (what did you love? what do you want more of?) Any cool resources, links, or tools mentioned during the workshopCan’t wait to see what you all took away from it!

150

PagerDuty Community TeamCommunity Manager 💚

[Workshop] Signal to Action: Modern Ops Centers with AIOps and Automation

Attending PD On Tour London’s workshop Signal to Action: Modern Ops Centers with AIOps and Automation session, led by Constant Fischer?Let’s get the conversation started!👇 Comment below with:Any burning questions you would like to ask? Feedback on the session (what did you love? what do you want more of?) Any cool resources, links, or tools mentioned during the workshopCan’t wait to see what you all took away from it!

140

PagerDuty Community TeamCommunity Manager 💚

[Workshop] Incidents to Insights: Run World‑Class Incident Management

Attending PD On Tour London’s workshop Incidents to Insights: Run World‑Class Incident Management session, led by James Pitcher?Let’s keep the conversation going right here!👇 Comment below with:Any burning questions you would like to ask. Feedback on the session (what did you love? what do you want more of?). Any cool resources, links, or tools mentioned during the workshop.Can’t wait to see what you all took away from it!

290

jnapalanNew Member 👋

Retrieving description of an incident via webhook step in an incident workflow

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?

442

6 days ago

velappsi_schNew Member 👋

Enhancement Request: Include Service Custom Field Values in the List Services API

Hi team,I’d like to request an enhancement to the List Services API (GET /services) that would make it possible to return custom field values directly within the service objects, without needing additional calls to the Service Custom Fields API.Current ChallengeToday, if you want to retrieve custom field values for all services in your PagerDuty account, you must:Call the List Services API to get the list of services Loop through every service ID Make separate API calls to fetch custom field values per serviceFor accounts with a large number of services, this results in significant numbers of API calls, higher latency, and increased complexity in automation and reporting workflows.Proposed SolutionProvide an optional query parameter (e.g., include[]=custom_fields) to allow the List Services API to return each service along with its custom field values in a single response, similar to how other PD APIs support the include[] pattern for expandable fields.BenefitsReduced API call volume B

100

9 days ago

xamiciCommunity Manager 💚

Meet the Speaker Lineup for PagerDuty on Tour London 🇬🇧

The countdown is on for PagerDuty on Tour London and the stage is set for the brightest minds in digital operations during an afternoon of actionable insights, AI innovation, and real-world stories from the frontlines of incident management.Meet the Speakers: 🎤 Yoann Fouquet – Senior Engineering Manager - Site Reliability at Bookoing.comYoann combines deep infrastructure expertise with management skills. He holds a PhD in Operations Research from the Université de Technologie de Compiègne and is an active contributor to the SRE community, frequently speaking at industry conferences like SREcon on topics such as Service Level Objectives (SLOs) and disaster recovery testing.🎤 Dave Hogan – Principal Architect, Service Reliability Engineering at WorkdayDave is a driving force behind digital transformation and AIOps at Workday. As a Principal Architect, he leads experienced engineering teams across the application stack, defining operations strategy and championing scalable SRE solutions

410

11 days ago

trevor-awNew Member 👋

Can I disable @mentioning the assigned user in Slack for low urgency incidents?

The new Slack integration update now @mentions the assigned user directly in the incident message posted to Slack channels. While this is great for high urgency incidents where immediate attention is needed, it's disruptive for low urgency incidents.Our team uses separate Slack channels and PagerDuty services for high vs low urgency alerts. Low urgency alerts have long SLAs and are triaged on a best-effort basis during business hours. Getting repeatedly @mentioned in Slack for these creates unnecessary noise and distractions throughout the day.Is there a way to control this behavior that I'm missing? Ideally something like:A per-service setting to enable/disable user tagging in Slack messages A per-urgency setting (e.g. only tag for high urgency)If not, would love to see this added as a configuration option. Currently there's no way to suppress the @mention without either muting the channel entirely or removing the native Slack integration, both of which lose visibility into the alerts

391

15 days ago

traillrobNew Member 👋

How do folks "re-engage" Responders

Hi folks, if a Responder who was previously deemed not needed for an Active Incident is now needed to be re-engaged, how do you accomplish this?

1232

18 days ago

xamiciCommunity Manager 💚