Recently active topics

Hello,I introduced some times ago a workflow plugin, allowing to create dependency links between jobs that can subsist over the 24h duration of the workflow, which is defined with a daily basis.This can lead, for example, with a job failing for any reason, and the jobs linked to it waiting patiently until the error is fixed, and relaunched. If needed, waiting for the whole night.Since, I’ve worked on tackling the main problem due to linking dozen of jobs together : a visual representation of the jobs and the links between them, through a new UI plugin.Preferably, with an interactive output and able to be updated at will.I’ve reached a satisfactory level with it, where while the desired goal is reached, the UI plugin became more than useful even for people not using the other dependencies modules.To the point it is becoming a companion of the main UI.The github repo is available here, with the usage documentation.As the new module in the plugin is mostly on the browser side, the install

Hello - we’ve been experimenting with the Scribe Agent in our incident workflows. The live transcription in Slack, and the periodic updates are great! We have a couple of questions:Are the Google Meets recorded for future reference? Is there a way to track people that join the bridge? Can we automatically add people that join the bridge to the Slack channel? Who owns or where do the Google recordings and transcripts live? Or is recording this in Google a separate action? Is the Scribe transcript exported anywhere - to the PD ticket or? Thanks for your input! 

Looking for your next deep dive into the world of DevOps, DevRel, and AI? We’ve got you covered with a two-episode drop! Built for Devs with Tessa Kriesel (Part 2)The conversation continues! In the second half of our sit-down with Tessa Kriesel, Daniel and Mandi dig deeper into the world of DevRel.Tessa unpacks how to build a stronger community around a product and how DevRel bridges the gap between engineering and the user. LISTEN NOW ⬇️ Harnessing AI with Lev AndelmanHow is the "AI Revolution" actually changing the day-to-day for Platform and DevOps engineers? Lev Andelman from Harness joins us to discuss the evolution of Harness Engineering. LISTEN NOW ⬇️ 🎧 Listen on Page it to the Limit or in your favorite podcast app: Spotify | Apple | Pocket Casts 🎧Page It to the Limit is a podcast that focuses on what it means to operate software in production. Hosted by the PagerDuty Developer Relations Team, we cover the leading practices used in the software industry to improve both system

Dear PD team,Your app plays a critical role in my team’s workflow but I struggle with the following problem:I can’t find a tone that is not too disruptive if an incident is triggered in the office but that is also loud enough to wake me up if I am in deep sleep.To get around this I manually switch between two different tones but this is a bit annoying and error prone.Is there any way I can automate this? I think this can be done by the iOS shortcuts functionality but would require the PD app to create App Intents exposing this? Many thanks,Dimitris

We recently upgraded to Rundeck 5.20 and set “rundeck.feature.nextUiMode.enabled = true”.  While the projects’ job lists load quicker (especially those with numerous cascading folders for job organization), the top of the screen shows duplicate search bars now.

Hello,Some of our users noticed a minor issue with "Job reference" step. There step label value is ignored. When a step label is added to a  "Job reference" step, the job can edition can be normally validated without any message error but the label value just disappears suddenly. It doesn't even appear after saving the stop (before saving the workflow)This happens in both Rundeck Pro/Enterprise and Rundeck Community…Is this a known bug?

Hello,When you add a "Job reference" step to a job, and choose “By name” to manually enter referenced the job’s group/name (rather then using “Choose a job” button and selecting a job interactively), is there supposed to be an autocomplete in jobs names/groups/names ? In both Rundeck Community and Pager Duty

We have enabled the execution history cleanup in Rundeck; however, the executions are not getting deleted as expected.As per the Rundeck documentation, it is mentioned that the cleanup feature needs to be enabled and properly configured. Could you please confirm:Is enabling and configuring the execution cleanup sufficient for automatic deletion? Or do we need to create a separate job to handle execution cleanup?We would like your guidance on the correct approach to ensure execution history is cleaned up as expected.And rundeck version is 3.3.11

For many organizations, the path to "elite client service" is often blocked by fragmented workflows and all-hands-on-deck chaos. At PagerDuty OnTour SF, we’re hosting a fireside chat with Jim Wallace, Operations Admin II at UWM, and Marty Jackson, NA Field CTO at PagerDuty, to discuss how UWM replaced manual intervention with a seamless, automated incident engine.UWM’s journey from a small storefront to an enterprise powerhouse required a radical shift in how they handle observability. Jim will share how they integrated PagerDuty and ServiceNow to drive Automated Incident Creation (AIC). Today, monitoring alerts trigger simultaneous actions across both platforms—instantly connecting the right teams and ensuring visibility for both technical responders and business stakeholders.A key highlight of their transformation is meeting responders where they already work: Microsoft Teams. By surfacing PagerDuty incidents directly within Teams channels, UWM has enabled its staff to acknowledge an

Hi all, quick vulnerability question.Our vulnerability software has flagged up Rundeck v5.20 with CVE-2026-22732 because of the component spring-security-web-5.8.15.jar I could not find anything about this CVE in this forum or Rundeck web page.How can we find out if there’s a fix for this coming up soon?Is there a place to report this?Thanks!

When you are managing thousands of services, "alert fatigue" isn’t just a buzzword—it’s a critical operational risk. At PagerDuty OnTour SF, we are bringing together incident leaders from Twilio and Intuit to discuss how they’ve moved beyond reactive firefighting to build resilient, AI-powered operations.Gandhi Kumar, Principal Incident Commander at Twilio, will share how his team navigates a staggering 60,000+ monthly alerts. By leveraging PagerDuty AIOps, Twilio has successfully cut through the noise, transforming a torrent of data into targeted, actionable signals. Gandhi will also provide a "view from the commander's seat," offering hard-won advice on maintaining calm under pressure and knowing exactly when to automate versus when to escalate to a human.Joining the conversation are Akshay Pratinav and Archana Kataria from Intuit, who will demonstrate their end-to-end automation framework for failovers and recovery. Their results speak for themselves: Intuit has achieved detection t

Hello,Is there a way to reference a job from another WITHOUT the referenced job’s project name ?Some of our users use the SCM plugin to push job definition to a GitLab instance and share the referenced same jobs between two Rundeck instances used for two different purposes. Lets call them Instance A and Instance B.Instance A has project_X containing a referenced job_1, from job_2. Both jobs definitions are pushed to GitLab instance and cloned to project_Y on Instance BThe problem is, while the UUID and jobs name are the same on both Instance A and Instance B because both jobs do the same EXACT thing as you would except (no modification on actual jobs, they different only in terms of which nodes they’re scheduled/executed on), projects names on tho other hand reflect the purpose/environment (testing, production, level-1 support…).That naming scheme leads to different projects name even when the jobs are the similar in terms of jobs contents (steps, scripts, commands…), thus project_Y in

As the role of the engineer evolves, we are moving beyond siloed AI tools toward a future of true agent-human partnerships. To explore this shift, we are excited to feature a session at PagerDuty OnTour SF with Jonas Nelle, Head of Engineering for Agents at Cursor, and Rukmini Reddy, SVP of Engineering at PagerDuty.This discussion will dive into how organizations can move from reactive recovery to predictive resilience. By utilizing protocols like the Model Context Protocol (MCP), teams can provide agents with a unified view of their codebase and PagerDuty incident history. This integration allows agents to bridge the gap between code logic and runtime reality, transforming them from first responders into "prevention architects" that flag risky patterns before they ever reach production.The conversation will also tackle the cultural shifts required for this new era. With the PagerDuty and Cursor MCP integration in mind, Jonas and Rukmini will share practical strategies for designing wo

We have our ServiceNow integration running, every now and then some incidents does not trigger PagerDuty and we get the following error in ServiceNow PagerDuty REST failed to trigger an incident: Requester User Not FoundIs there a configuration to allow servicenow users who do not have a pagerduty account to still trigger a pagerduty incident ? Research on articles is pointing me to have it set to Default User within ServiceNow so its not provisioning or require a PagerDuty account to trigger an incident

As we move from simply launching AI agents to maintaining them at scale, many teams are finding that the real challenge begins in production. When real-world data and unpredictable user behaviors enter the mix, maintaining quality can feel like a moving target. To help us navigate this, we are thrilled to welcome Richard Young, Director of Partner Solutions Architecture at Arize AI, to the PagerDuty OnTour SF stage.The partnership between PagerDuty and Arize isn't new; in fact, we’ve been working together for some time to standardize how we monitor our own internal agents. Our teams previously shared how we use Arize for "golden dataset" testing and regression-like frameworks to ensure our AI features—like the Insights, Shift, and SRE Agents—stay reliable as they evolve.Richard will be joined by PagerDuty’s Everaldo Aguiar for a hands-on session that builds on these foundations. Drawing on insights from over 1 trillion inferences and 10 million monthly evaluation runs, they will share

Hi,The table ‘stored_events’ grow exponentially, which each login of an user. Is it safe to purge this table ?Regards,Xavier

Catching up on the last month + what's coming next🎉 Recent HighlightsAgents Day Hackathon - LisbonWe headed to Lisbon to sponsor Agents Day, a high-energy hackathon that brought together 100 builders. The PagerDuty community showed up strong with 7 dedicated PD submissions! Huge shoutout to the LifeOps project team, who made it to the top 3 and pitched their idea live on stage.Want to see what was built? Check out all the submissions here.DevOpsDays AtlantaOur very own Mandi Walls took the stage in Atlanta to dive into one of the hottest topics in tech. Her talk, The Shallow End of Deep Learning, helped demystify AI for the DevOps crowd. Missed the session? Get the recap on the community forum.Page it to the Limit Podcast: Built for DevsWe were honored to host DevRel royalty Tessa Kriesel (CEO of Built for Devs) on the podcast. She shared her expertise on building authentic developer communities and why developer experience is more critical than ever. Listen to the episode here.🆕 Pro

I’m not finding an answer in the knowledge base, so posting here: On a Service, if I populate a link to a Confluence page runbook in the “Documentation Link” field, how exactly does that show up for responders on an Incident? I can’t see a placeholder or field on the Incident layout. The Knowledge Base states that “Once configured, responders can view the documentation link in the same section on a service's details page under Settings  Remediate.”Does this mean that the link won’t show on an incident for that service? 

Hey everyone,We're sponsoring Agents Day in Lisbon on May 1st and bringing a $1,000 bounty challenge for developers building AI agents with intelligent incident management.The ChallengeBuild an AI agent that integrates with PagerDuty to enhance your project with intelligent incident management, automated responses, or proactive system monitoring.We want to see creative integrations that showcase PagerDuty's capabilities – AI agents that monitor, respond to, or prevent incidents, and projects that demonstrate real-world use cases (even if simplified for the hackathon).Some ideas to get you started:A chatbot that queries PagerDuty for incident status and resolves issues via Slack A self-healing application that uses PagerDuty to diagnose and fix common problems autonomously A tipping agent for open source contributors who resolve incidents detected by PagerDuty Agentic alerting that reduces alert fatigue and aligns PagerDuty alerts with data insights from user's wearable devicesPagerDuty

Hello,Our users reported many of their jobs fail to run when scheduled with the following error… com.dtolabs.rundeck.core.NodesetEmptyException: No matched nodes: NodeSet{includes={hostname=node_fqdn.tld, dominant=false, }} at com.dtolabs.rundeck.core.execution.workflow.BaseWorkflowExecutor.validateNodeSet(BaseWorkflowExecutor.java:880) at com.dtolabs.rundeck.core.execution.workflow.NodeFirstWorkflowExecutor.executeWorkflowImpl(NodeFirstWorkflowExecutor.java:92) at com.dtolabs.rundeck.core.execution.workflow.BaseWorkflowExecutor.executeWorkflow(BaseWorkflowExecutor.java:220) at com.dtolabs.rundeck.core.execution.WorkflowExecutionServiceThread.runWorkflow(WorkflowExecutionServiceThread.java:95) at com.dtolabs.rundeck.core.logging.LoggingManagerImpl$MyPluginLoggingManager.runWith(LoggingManagerImpl.java:146) at com.dtolabs.rundeck.core.execution.WorkflowExecutionServiceThread.run(WorkflowExecutionServiceThread.java:77)Exception: class com.dtolabs.rundeck.core.NodesetEmptyException: No ma

We are monitoring network equipment and have 4 tunnels running over the same physical interface.  If there is a break in the connectivity at the carrier end that DOES NOT affect the local physical interface, all tunnels will fail.  This is an indication that the WAN circuit has failed.  PD sends 4 alerts for 4 tunnels with the same description EXCEPT the beginning which will be unique:Tunnel1 circuit1 Tunnel2 circuit1 Tunnel3 circuit1 Tunnel4 circuit1We have over 1000 of these circuits with 4 tunnels over each so doing this manually for each circuit would be a non starter.  My thought was that I could use a regex as a de-duplication key to get rid of the first word using ^\S+\s+(.*) and replace it with {{1}}. This way the above 4 alerts would all become “circuit1” for de-dup and the additional alerts would be suppressed.I can’t figure out where I would do this.  Is this something that I would need AiOps for?  Since we only monitor routers and switches, I can’t figure out what else I wo

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.

Hi all,On the previous forum, I posted:Hi All, Is there an upgrade available yet for the following vulnerability in the rundeck log4j library? Plugin Name: Apache Log4j 2.0-beta9 < 2.25.3 MitMPlugin ID: 282519Plugin Output:  Path              : /var/lib/rundeck/bootstrap/rundeck-5.12.0-20250512.war  Installed version : 2.17.2  Fixed version     : 2.25.3 I'm running rundeck 5.12.0. Thanks,Eric Racuna responded: Hi Eric, The engineering team is aware of that CVE, thanks for your feedback! Stay tuned to next releases. Regards! I checked in both 5.19.0 and 5.20.0 but it’s still not there.  Does anyone know when this is coming? jar tvf rundeck-5.20.0-20260402.war | grep log4j 24248 Mon May 12 16:40:32 CDT 2025 WEB-INF/lib/log4j-slf4j-impl-2.17.2.jar1811089 Mon May 12 16:40:32 CDT 2025 WEB-INF/lib/log4j-core-2.17.2.jar 30948 Mon May 12 16:40:32 CDT 2025 WEB-INF/lib/log4j-jul-2.17.2.jar302511 Mon May 12 16:40:34 CDT 2025 WEB-INF/lib/log4j-api-2.17.2.jar Thanks,Eric