Recently active topics

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

Hi,Has the database structure changed between 5.19 and 5.20 ? We experience a regressions issue and want to try to rollback to 5.19Xavier

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

I’m working on designing an Enterprise-level incident response and management system for our client using PagerDuty. We’ll be using the Enterprise edition and would like to understand the implications if PagerDuty were to go down. I know that PagerDuty is a SaaS service with a 99.99% uptime guarantee. In a worst-case scenario, for instance, if AWS were to experience a downtime, would PagerDuty also be affected? I need to design an alternative solution for this scenario as well. Additionally, I’m curious about how to determine which escalation actions were taken and which were not. Anyone has some thoughts? If you have worked on similar scenario, how did you approach that?

Hi,We just upgraded to PagerDuty 5.20. Since then, apparently, our IDS consider the new GenAI plugin as "malicious" and blocks its download.https://rundeckpro.tld/assets/pro/ui-components/GenAi.umd.min-85142c85b32d5e5ead5945256e58c753.js fails at 2.7MB (connection reset)Is there a way in the configuration files to completely disable this plugin, which we do not use ? It does not appear in the system (gear) menu as indicated in the docThis plugin does not neither appear in the plugin managerWith this problem, the UI takes dozens of minutes to loadRegards,Xavier

I'm trying to setup integrations in PD that will look at specific criteria and alert the service specified, while also having an existing integration alert on everything else - and it seems I can't have 2 different services for 2 different integrations with the same JQL Criteria.  For my team, we are instituting a “Functional Incident Manager”  who will respond to incidents only if the ticket is assigned to their team and the status is one that requires action.  For all other tickets, I want an integration to page a general “catch all” type of integration.  If I have the FIM Integrations active, and I have one for the catch all - with JQL I can add in the catch all integration to omit those in the FIM Integrations.  But - I can’t have it page the catch all.  It’s like I need to pick either the FIM integrations or the catch all integrations - I can’t have both. Has anyone else run into this scenario?  I’ve worked with my Atlassian admin, and the JQL and mapping are correct.

Hello.I noticed there is a weird difference between the two timestamps shown in Rundeck 5.19 web interface.I’m referring tot he HH.mm:ss timestamp shown in the left sidebar, which I assume to be the server’s timestamp in local timezone and the ISO8601 timestamp shown in tooltip/.rdlog file. The problem is they look inconsistent so I was wondering how each of these timestamps is determined The timestamp form tooltip/.rdlog file has a Zulu suffix which suggest UTC but there is a huge inconsistencyThe server is located in France (UTC + 2), locale timezone is set correctly in the OS, so is the UTC clock. NTP synchronization is active. Therefore on Rundeck server, both local timezone and UTC are set correctly.Rundeck JVM is executed with the correct timezone parameter “-Duser.timezone=Europe/Paris”. But the problem is there is much more than 2 hours differences between the left sidebar timestamp and the ISO8601 tooltip timestamps.I noticed the issue issue in job during it’s execution on the

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

Nice to meet you, I’m a beginner in pagerduty…I want to Integrate my Arduino/raspberry pi with pagerduty… How to write the syntax/code should i use for Integration for both Arduino/raspberry pi?.

Hello.While looking at one of our users jobs, I noticed Rundeck Community 5.19.0 interface doesn’t show all the logs in node view. Here’s an example in screenshot Ansible playbook executed by a Rundeck job’s step from a distant node.Rundeck “Nodes” view is broken, with empty space instead of logsSometimes more logs is displayed (a few seconds more) but never the whole logs. The job actually ends a while after that.Note that the same issue as the missing “whale of a log” link for huge log files. This happens with very small log execution files. The corresponding .rdlog file is only 337 kB and both the .rdlog file and “Log output” view show all the logs but “Log output” view doesn’t lose the nodes  context (what step has been executed in which notes) and users don’t have access to Rundeck server’s filesystem and thus can’t access to .rdlog files of their jobs’ executions.Also, for some reason, all the steps (Ansible playbook, most of it being cloning git repos) are considered as errors.

At our organization we generate PagerDuty incidents by using email alerts.The emails are sent to service integrations. Each service has an individual email. So even without Global Orchestration, we can process the emails into useful incidents using the Service Orchestrations. We aren’t licensed for AIOPs, so we can’t currently use Global Orchestrations.A typical email might from our SCOM monitoring and have a subject line something like  “ SCOM: Health Service Heartbeat Failure Resolution State: New” or from one of our storage systems like “Storage D1A: Warning filesystem <filesystem> at 80%”.This email is sent to our PagerDuty integration email and processed using the Service Orchestration rules. For repeated alerts, we can set a custom dedup_key such as the server name or filesystem name. If the dedup_key matches on subsequent alerts, then PagerDuty appends the new alert to the old ticket.In addition, the dedup_key allows us to close incidents indirectly by using an event rule:

Hi, first time poster. We really love our PagerDuty slack integration, and it’s been providing us excellent response times and clarity for our on-call rotation.We emphasize clarity of alert names, priority levels, affected services, and incident urgency in all of our alerts. We were surprised yesterday when all of a sudden, all of our alerts had emojis attached to them. This has made our experience very confusing and cluttered, and we’d like the ability to turn this off. Is this possible, and if not, is it possible to remove these entirely?

Hi everyone! 👋I’m Gurnish, a software developer from Gurugram, India. I primarily work with React and Vue, and lately I’ve been exploring backend systems and authentication flows as part of building an IAM (Identity & Access Management) platform.I came across PagerDuty while trying to better understand how real-world systems handle incidents, alerts, and reliability at scale. I’ve been exploring the platform and really like how it simplifies incident management and makes complex workflows easier to handle. It’s been interesting connecting these concepts with what I’m building and learning about system design.Looking forward to learning more from the community and contributing where I can! 🚀

Hello!Today we have one person on call from our department to handle incidents. We share this schedule amung us and we try to resolve incidents at our best abilities. That is ok.But during the work hours we would like the incident to go to the subject matter experts directly.I manage to get this to work by creating escalation policy and schedule for each subject, and restricting the schedule for work hours only, and duty watch as level 2 on the escalation policy.But this means that everyone gets a on call and off call alert every day. This is annoying. Each user can disable this I believe, but it is useful for the duty watch schedule.Any suggestions? :)

Hi PagerDuty community,I'm developing a mobile app for Ubuntu Touch in Python and QML to manage PagerDuty incidents, using the python api library (https://github.com/PagerDuty/python-pagerduty).I ran into a limitation when trying to implement notification.Currently, PagerDuty does not natively support UnifiedPush (https://unifiedpush.org), an open standard for push notifications that works independently of proprietary services like Google's FCM or Apple's APNs. This makes it impossible to receive real-time push notifications on platforms such as Ubuntu Touch, as well as on any other FOSS-friendly distribution i.e. where Google Play Services are not available.Would it be feasible for PagerDuty to add UnifiedPush support on the backend side?Concretely, this would mean allowing users to register a custom push gateway endpoint (a UnifiedPush distributor) instead of relying solely on FCM/APNs. The notification payload would then be forwarded by PagerDuty to that endpoint, and from there to