Recently active topics

Thanks for joining us at our live conversation with Spotify Backstage to discuss the new PagerDuty plugin. We weren’t able to answer all your questions live, so we’re adding all the Q&A to this thread for your convenience. Feel free to ask additional questions below! Question 1: Do we have the full scale service maps coming across from backstage to PagerDuty for better service support framework & health & impact view of dependent services? Answer: We have Backstage integrated with PagerDuty, syncing our service dependency maps to power Service Graph and impact chains.  Not a full “all-things” topology import: You’ll still manage Business Service structure and any non-service entities in PagerDuty for the best health/impact views. Question 2: Is there a difference in functionality between the PagerDuty plugin for Backstage and the one for Portal?Answer: There are no functional differences. It’s the same PagerDuty plugin and feature set in both. Question 3: Is there any video

The interactive morning workshop tracks for PagerDuty On Tour Sydney are officially out! Check out the lineup:🧪 Transforming Incident Management with AI OperationsFor Incident Responders, NOC Engineers and IT Operations TeamsDuration: 2.5 hoursDrowning in alerts? Struggling to separate critical signals from background noise? Your team deserves better than alert fatigue and endless manual triage. Discover how PagerDuty's AI-powered operations can transform your incident management—reducing noise by up to 90% and centralizing context so your team can focus on what truly matters.Topics:Intelligent Noise Reduction & Alert Correlation AI-Driven Context Gathering & Enrichment Centralized Incident Triage & Prioritization Service-Based Event Orchestration Actionable Insights from Complex Data Streams🤖 AI Agents & Automation: The Future of Incident Management​For SREs, DevOps Engineers and Platform TeamsDuration: 2.5 hoursStop fighting fires manually. Start building self-heali

The interactive morning workshop tracks for PagerDuty On Tour London are officially out! Check out the lineup: 🧪 Lab 1: AIOps Revolution Bootcamp: From Reactive to Proactive Incident ManagementIdeal for SREs, Incident Responders, Operations Managers, Platform Engineers, and DevOps TeamsDuration: 2.5 hoursTired of firefighting incidents instead of preventing them? Struggling with alert fatigue, high MTTR, and on-call burnout? It's time to break the cycle of reactive chaos. Discover how PagerDuty's cutting-edge AIOps capabilities can transform your incident management—reducing alert noise by up to 83% and enabling autonomous diagnostics so your team can shift from reactive firefighting to proactive incident prevention.Topics:Flexible Shifts with Intelligent Conflict Detection & PTO Management SRE Agent for Autonomous Diagnosis & Remediation AI Orchestrations for ML-Recommended Noise Reduction Scribe Agent for Automated Incident Documentation Insights Agent for Data-Driven Operat

I’m noticing a recent change in the mobile app where resolving an incident via swipe now requires an extra confirmation tap. Previously, a single swipe action would immediately resolve the incident with no additional interaction.This new flow adds extra time, especially when handling multiple low-severity or routine incidents. What used to be a quick one-gesture action is now a two-step process, effectively doubling the time required to resolve each incident.Is there a setting, or a way to revert to the previous workflow? I’ve disabled any requirement for resolution notes in the confirmation screen but it still requires that secondary workflow.

We use the ServiceNow V7 integration in production. It works fine, but we want to move to the generic V3 webhook. We have a lot of services on V7, so the plan was to switch just a few to V3 first and handle the rest later.In our test environment, when we moved one service to the V3 webhook, the other services using V7 stopped working. So we’re trying to confirm what will happen in production. If we switch a single service from V7 to the V3 webhook, will the remaining V7 integrations break? Or can V7 and V3 run side by side? We want to know if this is an all-or-nothing change.

Great news for Microsoft Teams users: you can now use Scribe Agent and leverage its intelligent incident scribing capabilities! No more scattered notes and less lost context while managing a crisis. Scribe Agent automatically joins your Microsoft Teams meeting, transcribing critical details right in your incident chat. With Scribe Agent, you can:Get real-time transcripts and smart summaries of incident meetings Receive context-aware status update drafts Quickly catch up on incidents with comprehensive summaries shared as soon as the meeting ends—and import them into post-incident reviewsWhether your team uses Slack or Microsoft Teams, Scribe Agent helps you reduce manual toil, easily keep your team in sync and focus on what matters. Watch the demo below and read our Knowledge Base article.   

My requirement is to repetitive alerts until issue is resolved, for an exmaple, someone in ,y team resolve the issue by mistake  but actual  issue is not resolved in this casr alert should be triggered in every 5 minutes bcz cloudwatch send only an alarm to pagerduty

I'm struggling with a job in Rundeck that includes an Ansible script, and I'm a bit confused about the node selection behavior.Is it possible to prevent a job from running on all nodes when “Change the Target Nodes” is unchecked? It feels contradictory that:the UI offers “Select All” and “Select None”,the job fails if no nodes are selected,but if you uncheck “Change the Target Nodes” entirely, it just runs on every node anyway.I assumed there must be a way to force explicit node selection before running the job, but I haven’t found anything in the documentation.This is the screen I'm referring to: 

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 ?

Hello, is there a way to "Kill tracked processes after execution" the PID child when i kill a job that running for a specific command(Not a job)?