Recently active topics

B me too much of the same way as to do it in the same group me too I and my friends and New Zealand vs and shyd and 

We get a published rotation of people covering the next 30 days from an outside vendor so the schedule changes every month. I don’t see an end date for a layer. - like starts Monday 3/16 and ends Friday 3/20. Right now the schedule just repeats ad nauseam even though we don’t have the schedule for April yet. Our old paging system allowed Start On and End On dates. Does PagerDuty have that mechanism?

Created our first Custom Field on a Service, a single select list to identify the Engineering Team responsible for that Service. I was hoping that we could set it up in a way so that when a responder receives an alert for a new Incident, since each Incident is paired with the appropriate Service, we could also display that Engineering Team custom field on the Service, at the Incident level. However, in reality it appears that the Custom Field on the Incident is not related in any way to Custom Fields on the Service.  Is it possible for me to display custom fields asociate with a Service, on incidents related to that service, so that on-call responders can see that info and I don’t have to manager an entirely separate custom field at the Incident level? Thanks! 

Hello everyone !Using Rundeck for a while (~2020), managing 2 instances for my company, here to lurk some information about issues, fix, problems and solutions of course ! Have a nice day !

have a nice day with rundeck :)  🙂 

Catching up on the last two weeks + what's coming next🎉 Recent HighlightsPagerDuty On Tour - LondonPagey claw machine at our Play ZoneOur flagship event brought together 160+ attendees for an incredible day! PD Commons ran a Play Zone featuring a Jeopardy game that had 40 people competing—including a customer who's been with us for 14 years! Missed it? Check the speaker lineup on Commons.DevOps Not Dead Conference - LondonDaniel Afonso (aka sir Page-a-Lot) took the stage in full knight armor 🛡️ to deliver his talk on The State of AI in Incident Response. When the conference theme is fantasy, you commit to the bit.AWS User Group Lisbon x Cloud Native Lisbon MeetupOur Lisbon office hosted Debugging & Incident Response in the Cloud Native Era with 60 registered participants. The energy was high—folks stayed until 10pm, demolished 22 pizzas, and cleared 3 boxes of beer. That's what we call a successful meetup. 🆕 Product & Partnership NewsSpring '26 ReleaseIntroducing the Path to

good good good

Hey Community! 👋We all know the pain of "noise"—the alerts that don't matter, the context-switching that kills focus, and the manual toil that keeps you from building cool stuff.To help, PagerDuty University is running a 6-part deep dive into AI-Powered Operations. We’re skipping the high-level fluff and getting into the "how" of building a more resilient, automated operating model.Each 30-minute session covers a specific pillar: Noise Reduction: How to actually get to the root cause without the static. Accelerated Response: Using AI to automate the "boring" parts of the incident lifecycle. Resilience & Compliance: Best practices for scaling your ops without losing control. Whether you're looking to optimize your current setup or see what the latest AIOps features can actually do for your workflow, these sessions are built for you.👉 Check out the session lineup and grab a spot: https://university.pagerduty.com/page/ai-powered-webinar-series

We're excited to announce our latest release focused on autonomous operations – transforming how teams handle incidents with AI-powered capabilities built on 16 years of operational intelligence.What's New:SRE Agent as a Virtual Responder – No more 3 AM wake-up calls. Add SRE Agent directly to schedules and escalation policies as your first line of defense. It detects, triages, and diagnoses incidents before paging humans, with full control over permissions and remediation approvals. Plus, it learns from past incidents to continuously improve.Coming soon: SRE and Insight Agents for Microsoft Teams, enhanced Scribe Agent with conference bridge chat ingestion, and AI agents available in the Web UI.Full Lifecycle Incident Management in Slack & Teams – We're eliminating context switching with dedicated incident channels, threaded updates, and SRE Agent embedded directly in-channel. Our modernized Slack experience is live now, with Microsoft Teams enhancements rolling out soon, plus pre

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?

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

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

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?

We are excited to announce that the details for PagerDuty on Tour San Francisco are officially locked in!Mark your calendars for a full day of connection, learning, and innovation as we explore the path to autonomous operations.📍 The DetailsDate: May 13, 2026 Venue: The Mint (88 5th St, San Francisco, CA)🎤 Speaker LineupGet ready to hear from industry leaders and PagerDuty executives, including:Jennifer Tejada (CEO, PagerDuty) David Williams (SVP Product Development,  PagerDuty)Rukmini Reddy (SVP Engineering, PagerDuty) Customer Speakers from Intuit, Twilio, Clover, UWM, and Arize AI sharing real-world stories on AI-powered incident management and automation🛠️ Hands-on WorkshopsKick off the day (8:30 AM - 11:00 AM) with interactive sessions designed to level up your skills:AIOps Revolution Bootcamp: Learn to shift from reactive firefighting to proactive prevention. PagerDuty Incident Management Certification: Validate your expertise in best practices and frameworks. Fast Track: Foun