Introducing PagerDuty Commons - Your New Digital Ops Community Hub!
Ask questions, find answers, get inspired
How can I setup okta with rundeck community
We are currently using the PagerDuty extension called ServiceNow (v7) to integrate with ServiceNow. We are upgrading our ServiceNow integration to version 8. The webhook does not work the same and appears to lack the same functionality as the extension, so we’d like to use the v8 extension. However, it appears that the V8 extension is not available in the dropdown: Is the V8 ServiceNow integration compatible with the v7 extension? Or is there some other way for me to get the V8 ServiceNow extension? Or something else that I am missing?
Hi, I want my team to be on call 3 days at a time, with no weekends. This doesn’t seem to be possible, when I add the restriction of Monday to Friday, the scheduling of the 3 days for each person still runs into the weekend.I even tried to add another layer with just one person on it at weekends to try and block these days out, but it still doesn’t work.You can see in the image for example 6th December, Jake comes on the rota for only half a day, because the schedule is still running him through the weekend, even though weekends are excluded.It should be (from the start)David - Monday Tuesday WednesdayJake - Thursday Friday MondayMark - Tuesday Wednesday ThursdayGerald - Friday Monday Tuesdayetc. Surely this is a relatively common requirement - there must be a way I can do it? What restrictions do I need to set? Any help would be appreciated!Thanks,Davidcurrent restriction config
Is there a way to enforce that a custom field is populated when resolving an incident? Our current use case is to create a custom field for Categorization of the resolution. However we don’t see anyway of enforcing that it gets updated. Without enforcement then we are just running audit reports and chasing people down. Not the best use of time. If there was a way to enforce that the field gets updated, that would remove this concern.
Back in 2021 I created new services with Global Event rules to replace the services with email integrations. Now with the new Event Orchestration coming I need to convert them. But for the life of me I cannot find my Global Event rules. It’s been that long since I had to change anything in PD so I am rusty. Want to get them converted before Jan.Any help would be greatly appreciated.Thank you, Vito.
Hi team,My company manages PagerDuty configuration in terraform. One resource we manage is a PD Slack connection. From this doc, it mentions this resource requires a `user_token` API key. https://registry.terraform.io/providers/PagerDuty/pagerduty/latest/docs/resources/slack_connection My question is, what happens when the user leaves the company? Will the user API key become unusable?
Calling Our Esteemed Operational Resilience Network, 🛡️We're excited to announce an opportunity to participate in PagerDuty's Early Access program! 🚀 This initiative allows select participants to test and provide feedback on upcoming features before their official release.Key Benefits of Participation:Preview cutting-edge incident management tools 🔍 Influence product development through your feedback 🗣️ Gain a competitive edge in operational efficiency 📈Current Early Access Features:Event Orchestration External Data Variables: Enhance automation capabilities with dynamic orchestrations 🤖 Operations Console with Alert Side Panel: Streamline incident management with a unified dashboard 📊 Incident Types: Customize workflows for specific incident categories 🏷️ [Product Tour] Service Reassignment: Improve incident routing for faster resolution ⚡ Operational Maturity Model: Receive data-driven recommendations for operational improvements 📊This program offers a unique opportunity to
For many teams, implementing end-to-end automation in one go is too much abrupt change. A "crawl, walk, run" philosophy is better. For maximum value, automation should be embedded throughout the incident life cycle — all the way from an incoming event signal to final resolution and learning. But for many teams, implementing end-to-end automation in one go is too much abrupt change. By Joseph Mandros, Product Marketing Manager at PagerDuty. Read more ➡️ The New Stack
does anyone aware of the audit or report that we call pull where the person is on call but never recevied a notification ?
This week, Groundcover CEO and Co-Founder Shahar Azulay joins us to talk eBPF and what’s next in observability.Listen now: https://www.pageittothelimit.com/epbf-with-shahar-azulay/Shahar Azulay, CEO and Co-Founder of groundcover, the company reinventing the cloud-native application performance monitoring domain with eBPF, is a serial R&D leader. Shahar brings experience in the world of cybersecurity and machine learning having worked as a leader in companies such as Apple, DayTwo, and Cymotive Technologies. Shahar spent many years in the Cyber division at the Israeli Prime Minister’s Office and holds three degrees in Physics, Electrical Engineering and Computer Science from the Technion Israel Institute of Technology as well as Tel Aviv University. Shahar strives to use technological learnings from this rich background and bring it to today’s cloud native battlefield in the sharpest, most innovative form to make the world of dev a better place. 🎧 Listen on Page it to the Limit or
Hello, I would like to integrate OPenNMS with PagerDuty for new snmp traps received. So if a snmp trap is received it would send a create event to Pagerduty for the corresponding service?
Hello, I am new here and looking for some help/direction.What: our company uses Teams and I want to give our support staff a button in our SEV-1 channel that they can push that will page out for on-call staff to attend the triage call.Why: we are seeking a “faster than calling the support number” means to initiate incident response.for customer reported issuesIs there a simple way to achieve this?
Hello everyone,I am facing a challenge with setting up alert routing for Kubernetes clusters using Prometheus and PagerDuty, and I wanted to seek your advice or suggestions on how to solve this. ### Problem:We are currently using Prometheus rules to trigger alerts and send them to PagerDuty (PD) for our Kubernetes clusters. At the moment, all our alerts are routed to a single PagerDuty service. Now, we need to separate these alerts based on labels in the Prometheus rules to ensure they are handled by different teams. Specifically:- We want to route alerts for different teams based on labels defined in the Prometheus alerting rules.- Each team should have its own escalation policy within PagerDuty, but we must keep using a single PagerDuty service.- Unfortunately, we can't use the **AI Ops feature of PagerDuty** to help with this segregation. ### Example:We have two teams, **Team A** and **Team B**. Alerts for these teams should be routed based on a label in the Prometheus alert rules.
Our use case seems to be the opposite of what PagerDuty currently supports. I know we can use the Dedup Key to merge alerts into an already open incident and help with grouping alerts. However our use case is to not send a notification unless we have received X number of alerts in Y time. What we see is that a run will fail, but the next run in 15 mins is successful, so our on-call person is getting paged and then resolving the ticket because the next run was successful. Would be good to not page the On-call person unless the next run also fails. But haven’t seen how to handle this in PD. The Auto-Resolve doesn’t work in our case because they are individual alerts - from seperate runs of a pipeline - the dedup key is what links them. Has anyone dealt with a use case like this? Have you been able to solve it?
We have a use case that looks to not be supported by PagerDuty, wondering if anyone has a way to implement this scenario.Our pipelines are dependent on 3rd party APIs. When there is schedule maintenance of an API, we would like to be able to disable all alerts related to pipelines that are dependent on that API. I have looked into setting up the API as a dependent service, but it doesn’t look like I can do anything with this linkage to suppress alerts.
We’ve recently upgraded to the newest version of the PagerDuty integration in ServiceNow.Now what we are finding is that sometime, the priority is not added to the ServiceNow incident that is raised. Most of the time things work fine. But sometimes, an incident is created with no priority.Most days we get one or two. Some days we get 50+.I can see no pattern to what’s going on. Times are random. Counts appear random, and most of the time it works fine.I’ve enabled debugging on PagerDuty, even added a few logs in myself, but I’m not able to see any actually issues.Has anyone come across this? Does anyone have an ideas on how I might move things forward?
We have upgraded to Webhook3 and have all intergrations intact howevee still we have observed duplicate incidents created by PD in SNOW. Please advise if this is known issue.
Expert-level, in-depth, and practical guides for practitioners
Learn about PagerDuty, get support and find latest releases
Customize your experience with with PagerDuty APIs
Your source for on-demand PagerDuty training
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.