Save Your Virtual Seat: Demo Roundups! Webinar Series
Ask questions, find answers, get inspired
Hi everyone,I’m part of a IT team working to unify our incident response with infrastructure automation, and we’re exploring better ways to integrate tools like Ansible, Rundeck, or Attune with PagerDuty for real-time operations.Here’s what we’re trying to achieve: Automatically trigger predefined scripts or runbooks (via Rundeck or Ansible Playbooks) when certain PagerDuty alerts are fired Create custom PagerDuty services for various infrastructure tiers (e.g., DB layer, web servers, networking) with tailored responses Ensure clean logging, rollback, and audit trails for all automated responses triggered by PagerDuty incidents Tie notifications to team roles or escalation policies based on specific server groups or alert types Has anyone here successfully set up something similar?We’d love to hear: What integration method worked best for you (webhooks, APIs, plugins)? Any challenges around permissions or security controls when executing remote tasks post-incident? Advice on
Today’s GCP outage is hitting hard. We see you. We’ve been there. If you're on-call, in the incident room, or just trying to keep your systems afloat, this one's for you. Here are 6 tips to help you survive days like today.👇 1. Breathe.Before you dive in, pause. Stay grounded. Clarity matters more than speed when everything’s on fire. 2. Triage, Don’t Troubleshoot Everything.Find the impact surface first. What’s customer-facing? What’s internal? Prioritize based on real business impact. 3. Use the Buddy System.Nobody should suffer alone. Assign a comms lead, a responder, and a runner. Rotate. Burnout is real. 4. Use Runbooks & Checklists.Now’s not the time to rely on memory. If you’ve got docs, use them. If not, write down what you learn, future you will thank you. 5. Communicate Early and Often.Don’t go dark. Internal teams and customers want updates, even if it’s “We’re still investigating.” Silence creates chaos. 6. Debrief After, Kindly.Postmortems aren’t blame sessions. They’
Hello, everyone! How to stop PagerDuty from paging onshore L2 (via phone) team after offshore L1 acknowleges the page (via email)? Thank you!
After a small chat at PagerDuty on Tour London, Avantika Iyer joins us to chat about IDPs, give us a story lesson on Backstage, and give us a glimpse into its future.Avantika Iyer is a Engineering Manager at Spotify and leads the delivery of Backstage’s open source and commercial products. Listen Now: 🎧 Listen on Page it to the Limit or in your favorite podcast app: Spotify | Apple | Pandora | 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 Community Team, we cover the leading practices used in the software industry to improve both system reliability and the lives of the people responsible for supporting it.
We’d like to see the metrics on the Dashboard (under the Over Time section) filtered by Business Services.Some of our business services have more than fifty technical services so it is impossible for the management teams to use it.On the Dashboard it should also provide a link to the Insights/(Business Impact), just like all the other sections do.
Walking into a tech conference hall can be overwhelming. Tons of exhibitors trying to catch your attention with the latest industry trends, and you only have 30 minutes between one talk and the next, or that important networking meeting you’ve scheduled.Why not ask for a little help from your AI friends to use your time wisely and go straight to the booth that will show you what is really important for your operations?That's exactly what this PagerDuty customer did during AWS Hamburg this week. 👀 Look what they got:
Hello folks,I would like to clarify whether I can trigger alerts by sending an email to PagerDuty or by calling support line. Does anybody know how can I do it? I am on a free plan.Thank you in Advance for your answers,
🚀 Check what’s new in PagerDuty and come back to let us know…
Our existing incident mgmt process includes an escalation policy which always initiates our product engineering team. The process rings through to several team members until someone joins the incident from that team. They would like to be the first initial single point of response to all incidents. However, sometimes they would like to reassign the incident to our cloud team. Is it possible to create an additional escalation policy which rings through to a set of individuals from our cloud team based on reassignment of the incident in Pager Duty? If so, are there any best practices on how to accomplish this?
Has anyone faced similar issue while updating sound over ios app
Our open-source API client for Python has now been refactored from a monolithic one-file module into a multi-file module. This change is being made to fulfill a need for long-term maintainability and improved readability. This new release does not add new features, but aims to make contribution of new features far easier going forward, most notably enabling us to add a py.typed file to enable using typehints in projects (issue #26). More about this release:https://github.com/PagerDuty/python-pagerduty/releases/tag/v2.0.0https://pagerduty.github.io/python-pagerduty/changelog.html
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.