PagerDuty

The PagerDuty platform is used across the organization for on-call management, event/alert management and automated escalations. The platform solved a significant inefficiency within the business related to on-call and escalations. Prior to PagerDuty, escalations were manual and not well documented. This made it difficult to hold people accountable and properly document problems. Through PagerDuty's escalation policies, on-call schedules and general workflow automation capabilities, the problem was solved fairly quick. Because our on-call team members are paid each time they answer an on-call request, this made tracking the notifications much easier.

I'm using PagerDuty as administrator and Manager. Followings are the operations I'm doing.

• Create/update/delete the teams.
• Create escalations policies.
• Create schedule for teams

Business cases:

• Incident Management
• Alerting management
• Page on-call users.
• Integrations with 3rd party applications like Slack, AWS, Emails, and Jira.
• Configure workflows in 3rd parties for e.g. on-call person schedule for a team in Slack.

We primarily use PagerDuty for on-call alerting. We have a number of monitoring platforms that are integrated with PagerDuty or send emails to escalation policies for various teams across the org. We are able to maintain a schedule of individuals in each team and we are able to escalate alerting should current on-call fail to pick up the page.

1. Automated deployment of infrastrucutre
2. Automation of issuing vpn certificates.
3. Automated reporting for various use cases
4. Aumated configuraiton deployment of services

PagerDuty for us is a critical tool, rather it's for after-hours paging or raising awareness of a critical issue during the day. Part of being an IT is managing multiple systems, which can be on-prem or in the cloud, and when these systems have issues or are down, we need to get timely alerts from our RMM tools. PagerDuty makes this possible; using their application, we can set on-call rotations, backups, holidays, and substitutes and make sure that we have a hand on the wheel when things get bumpy. PD can tie directly into applications as a 3rd party plugin, which as the #1 solution, is widely supported, or there is the option for SMTP triggers. Businesses need PD, so IT can get those critical alerts to keep the business on track. I have tried comparable solutions and always find myself coming back to PD.

PagerDuty handles our on-call alerting. This means when we have production level outages or issues, they get sent to PagerDuty and PagerDuty has a schedule for our on-call engineers and can send texts, emails, Slack notifications, and phone calls to the correct person to handle. Within PagerDuty we setup schedules so we know who is primary and who is secondary on-call so that way we always have coverage.

We use PagerDuty to get real-time alerts for disruptions and outages. I have been using it for a year, and haven't had any issues whatsoever so far with it. Aside from the alerts, it has allowed us to significantly cut time on repetitive tasks when we have to declare a major incident that needs to be tackled by multiple people. We have integrated it with IM and video call: when the person on call gets an alert and deems it necessary to involve multiple people, they just click on a button, and the necessary people get notified via an IM message that contains the PagerDuty alert URL, and a video call link where they can join the rest of the team. This way, we just start doing the work that matters, which is tackling the issue at hand. Very happy with the product and the support service.

We utilize PagerDuty for incident response -- so if something critical happens where we literally need to wake people up, this is how we do it. We have it integrated with our other systems so that there is a clear workflow and notification associated with any triggering event. Specifically, if an incident of a certain severity occurs, PagerDuty sets off an alert across multiple systems in support and engineering, pinging them on their phones, and mobilizing a response team

We used PagerDuty to manage our Out Of Hours support when there were site issues. It was useful to escalate calls and have a clear log of Who answered which issue, what time, and when issues had been resolved. It was also useful to handle and schedule the support rotas. Integration was fairly straight forward too.

We use pagerduty in our clients information system to recover, analyse and create alerts based on the cloud provider logging service.
PagerDuty is then configured to send alerts to specific users

We used PagerDuty primarily to manage on-call rotations across multiple engineering and support teams and to route automated alerts to the correct people in correct engineering teams. We also used it occasionally to route urgent (24/7) customer support requests to the correct people in product support departments. Additionally PagerDuty escalated incidents when they were not acknowledged or resolved promptly, and we used it as a tool to analyze data about the causes of frequent issues.

Pagerduty is used both for alerting teams to application problems that are identified by our monitoring and observability platforms as well as engaging on-call resources into an active incident bridge for real-time troubleshooting and remediation.

PagerDuty was used on our on-call rotation for Technical Support Engineers. If a request came in from a customer outside of business hours, it would trigger PagerDuty to page the on-call engineer. We typically had engineers on-call overnight or on the weekends, so PagerDuty allowed them to be away from their station but still be alerted if an issue came up.

We use PagerDuty for engineering incident management. It alerts us about issues in our production pipeline, and offers escalation policies and alerts so we can address the SEVs in time. By paging the on-call engineer to look into blockers in a timely manner, it allows us to improve our service metrics.

For alerting purposes, we have integrated PagerDuty with messaging application and for all network alerts, we directly get the notification in our application, so we don't need to have a separate application for the same. We also have enabled emails for notification which help the teams to work on the issue as soon as possible

We use it for off-hours support and managing notification schedules of off-hours support staff. It simplifies management with notification of schedule hand-off and backup coverage.

PagerDuty is used as an event management platform. All monitoring tools used are supposed to feed into PD and the logic of whether the alerts are high / low etc are performed in PagerDuty . This makes it easier to manage and each team works in a similar way.

PagerDuty is an incredibly tool for managing response and incidents and I find it very effective and efficient. To people who are non technical skilled it is very friendly and easy to use since it has dashboard that is easy to understand and straightforward. When it comes to observation the app top notch like one can set alerts with notifications in way that when something goes wrong there is a fast action. It is crucial to have product that will aid in monitoring your program development architecture so as to detect, diagnose and resolve any incidents which may have adverse effects on your final products.

We use PaperDuty to manage our production support on-demand schedule. With the tool, we plan the team availability for each group of services. When we're on call PagerDuty notifies us (via slack, mobile app, and email) about the issues so we don't lose any alerts, and also it handles the escalation policy as needed automatically

We're using PagerDuty for reliability services such as service monitoring, on-call handling, on-call alerting and helps in managing infrastructure based alerts and outages in our systems automatically.

In my current and previous production system Datadog and Sumologic are tools used for observability and they are configured to send alerts to PagerDuty for errors or warning as per user/customer specific thresholds. We are using webhooks to implement this integration. We have customer specific rule sets and thresholds.

PagerDuty helps us seamlessly manage our on-call rotation without needing to carry a bat-phone or manage a godawful excel spreadsheet. Developers and site reliability engineers create their rota's and overrides, and our world keeps turning.

PagerDuty is the leading digital operations management platform for businesses, PagerDuty is an end-to-end incident management and response platform that provides developers, IT operations, and business stakeholders the insights they need to resolve and prevent business-impacting incidents quickly . We use Pager Duty as ticketing tool for my company , we have other products in the infrastructure and any alerts will go to Pager Duty creating tickets which then can be looked upon for resolution.

PagerDuty was used for routing notifications for oncall issues to the oncall person. This allowed the proper person to be notified when we had an production oncall issue.

We used PagerDuty (PD) in our CS team to get alerts when urgent customer requests would come into support. Our engineering team would use it to send urgent alerts to the on call contact in the event of a system failure or abnormality that was time sensitive.