Issues that use to "fall through the cracks" or receive no attention/acknowledgement at all have been almost eliminated totally. The time for a technical resource to be alerted to an incident and acknowledge it has gone from 15-25-35-45mins to 5 minutes or less. Teams are now proactively alerted to issues that may turn into something big before the customer notices any impact.

PagerDuty is incredibly easy to setup and use. Creating new teams, on-call schedules, and escalation policies can be done in a matter of minutes. You can go from manually looking up people via a google calendar or an excel sheet, to engaging an on-call resource in 2 minutes or less from the great app while you are on the beach. The integration with Slack is great, no other way to say it. Very useful for incident notifications for those teams that rely heavily on Slack.

The reporting functionality of PagerDuty needs some further enhancements. Obtaining certain data such as "what users are using which contact methods" for example still needs to be provided by contacting their Support team. The filtering of the Visibility console needs work and is currently limited to "All Teams" or a single team.

We were tired of paging everyone all the time on things going down or coming back up. Now it pages one person during business hours only. Also if the server comes back up it'll close the ticket for us and resolve the call. Our admins can now sleep at nights and not have to respond to every page with people trying to figure out who is handling the situation.

Most? There are so many features with pagerduty. I like it only alerts one person on call instead of the old way we use to page people. We use to page everyone on everything. Now it's just the person on call and he doesn't respond it goes to the next person. Very nice setup.

Scheduling times is a bit difficult for me to grasp, but once you figure it out you only have to set it up once.

Very fast and reliable notifications. The mobile app is great to use for acknowledging and resolving pages.

Confusing setup for simple services. Should have a streamlined process to set up user, team, service, and escalation policy in a few clicks.

PagerDuty gives us peace of mind. With PagerDuty it's great to know that the right person will be contacted as soon as a production incident is logged. Keeping track of who is on support is no longer a hassle. I can't imagine us managing production support without it, especially considering the fact that the team is spread across multiple continents. I can't recommend it enough!

- Great integration support - Mobile app works great and continues to get frequent updates - Flexible configuration options without being overly complicated - Allows us to easily manage our after-hours roster and schedules - Ability to create incident reports is a great time saver

- Pricing is a bit more than some competitors

I have used pagerduty for years, and I have to say I use it as the gold standard for other notification services. So far, competitors either don't have nearly the same level of features, or cost a fortune.

Easy to set up. Inexpensive. Reliable. It has a number of integration options for various monitoring systems, and they are always adding more. They also have generic versioned APIs for any custom software you might bring to the table.

The Mobile app sometimes has issues refreshing when there is a lot of activity.

Web application is seamless and we had to contact support for any kind of question.

Seamless workflow management, once the workflow is setup everything works just as expected. PagerDuty has many integrations which allows us to setup alerts just by choosing the application, which is a great thing for small teams where development costs are very high.

Cannot think of anything from my standpoint, we are a small team and PagerDuty has everything we need and it works as expected every single time.

PagerDuty takes the complication out of scheduling and lets us focus on keeping our services up and healthy. We set the schedule and forget about it.

The Terraform provider is very buggy. We often find we have to go through multiple rounds of guess and check to get Terraform config to match up with how we want it to end up in PagerDuty. I understand that Terraform is not the primary UX you are focused on but for Terraform power users managing many teams and services it is indispensable.

PagerDuty helped our product to become highly stable and it ensured high availability to the end user, overall had a great experience with it.

PagerDuty is used to send alert notifications to developer, We can use it in a way that when ever failure occurs notify the developer who is scheduled to be on-call, Even a customer escalation to a email can trigger a pagerDuty notification alert, when the receiver email ID is subscribed with PagerDuty, PagerDuty has escalation policies , in which multiple users can be in different level, if level 1 failed to resolve the issue, the level 2 dev gets a alert etc .. and the dev's can be scheduled to rotate there levels in fixed time intervals, like weekly bases, It Dose a good job of maintaining the issue states & the alerted issue has different lifecycle such as triggered, acknowledged , resolved, snoozed, It maintains analytical dashboards on dev's which shows the responsiveness of the developer , like how many issues they have resolved and what is the average resolution time or have they escalated it etc .. it maintains history of alerts, it has good customer support, the resolution note's can also be added against the alert, We can configure the alerts as Low and High Urgency , based on which we can have different type of notifications, types of notifications are phone call, message, email, push notification in pd app etc ... pagerDuty deduplicates the alerts with same message, if a incident is in open state and if same incident occurs again and again , it will not be raised.

Sometimes when i resolve the alert on web, i still get a call on phone, If the incident was resigned by the developer to a other user who is not in the escalation policy and if he did not answer the alert the escalation chain stops, instead it should be thrown back to older escalation policy from ware it begun

I started trialling PagerDuty and other alert aggregation services after accidentally sending myself 10,000 emails. One thing PagerDuty does and does well, is cut through the noise, and helps you focus on the actionable issues. With integration with almost every alerting tool out there, including basic email - integrating a PagerDuty alert into your application or service is far too easy. The pricing is reasonable, and the phone and SMS alerting options work well, even in New Zealand. The PagerDuty app itself makes being on call so much easier, with simple acknowledgement and resolution actions, next to escalation and incident collaboration features. Having user controlled customisation, you can setup the alerting to suit your connectivity and support your sleep. After 6 years on call for a critical NZ wide system, I can say PagerDuty is refreshing change to the game. Don't hate the pager...

Simple setup and easy first alert. Comprehensive incident management, reporting and analytics to focus on what matters. Highly configurable alerting that is controllable by the recipient themselves. Easy escalation, resolution and communication features in mobile application and via the web. Well supported SMS and Phone alerting and incident management - Internationally Quick and easy support for the product - from a great PagerDuty team. Less noise, more actionable alerts with comprehensive de-duplication and alert filtering options.

PagerDuty is unforgiving of poorly written interfaces generating errors and despite ignoring ones' phone while in meetings, the alert will get to you, no matter what you are doing! While I love the 'PagerDuty' alerting and am amused by the 'Engineer Laughing' alert sound - having more options for custom, per incident, alert notification sounds in the Mobile app would be great.

PagerDuty is the best incident management platform out there helping manage incidents across our platforms to manage issues and centralize all of them in a centralized place.

Integrations can be tough and confusing to make happen is the one big gripe I have with PagerDuty, some times it feels like there isnt a single standard.

My overall experience it's that it's a great product. If you need an incident management tool it's the best in their sector and it works as expected but it lacks of some basic features and a really bad documentation that will drive you crazy.

What I like the most is the perfect work Pagerduty does at its job, alerting and incident management. We can get alerted in a very granular way, the alerts are great, the statistics about previous alerts too. It just do what you need it to do.

The things I dislike is the really bad documentation PagerDuty does and the horrible User Interface, you never find what you need to find. Also it needs some necessary features that for any reason people are requesting from years ago and they still not working on them like the ability to leave empty on-call schedules (due to bank holidays or vacation)

Overall, PagerDuty is good product which can be considered if you're running some critical services, infrastructre in your organization.

Followings are the PagerDuty benefits: - It is a SaaS based alerting systems allowing companies to use their in house technology for incident response. - It provides the realtime monitoring for all the infrastructure and services. - It provides a lot of integrations with other products for example Jira and Slack. - PagerDuty has a level of escalation setup that allows incidents to follow a process chain. - PagerDuty features like SSO, RoleBased Access.

Followings are the Cons for PagerDuty: - It is expensive as compared to its competitors. - Its integration lacks some features like easy set up. - It has a way to improve its configurations so that a user with zero technical knowledge can understand it.

This is a good way to keep our applications in a highly available state, it is really useful and great tool to have

This Tool is simple and effect, the sole purpose of this tool is to alert the developer, and keep track the alert was resolved or not, so , there are escalation policies that can be defined, such that when a primary user dose not acknowledge the alert, it wold be escalated to a other user in the list ,order wise there are different type of alerts hards and soft, so we can set different notification methods for both, supported notification mediums, phone call, SMS, app notification, email etc.. We can add note for all alerted insedents, we can see the history of alerts and to come to a conclusion and fix it for a long term, they have a great support team

I don't see any issues with the service, some times even if we resolve the alert in the web UI, we still receive the call

Having PagerDuty set up to trigger alarms to will notify my team is truly priceless. Whether we are on duty, or in an On-Call scenario, PagerDuty is always around to let us know when things go wrong.

I love how reliable PagerDuty is. My company has PagerDuty implemented for not only our On-Call regiment, but also with alerting. Since we've been using PagerDuty, we've ALWAYS been notified of issues that we've created alerts for. Sure, it's not always fun to receive a call when On-Call, but we can always rely on PagerDuty to be functioning correctly to ensure we are informed in the most critical of moments. Keep up the good work!

No cons to report, honestly. Other than having a critical moment where PagerDuty is having to be utilized. However that is no fault of the PD Team!

Without PagerDuty we could not run our on-call rotation. The learning curve is pretty steep, but once you have things configured correctly its a fantastic tool

- Love the on-call rota, the ability to schedule overrides and multiple call out hierarchies - The wide range of alerts and abilities to interact with the product via multiple channels - Integrates with most tools natively, and there is always email alerts to fall back on - Ability to customize alerts based on email content

- The learning curve is pretty steep - Suffer from alert overload and the AI features are extra

Easy implementation, good support

Great two way communication with LogicMonitor. Only product we found that would stop the on call alert when the LogicMonitor alert cleared.

There is no way to notify a non licensed user when the on call schedule. We’d like to have our team DL emailed whenever an on call changes.

Our experience has been good, but it all depends on your implementation. If you don't plan your implementation and set your rules properly, you're going to have a bad time. Read through the implementation guides and best practices before you pull the trigger on making this product live.

PagerDuty makes it so easy to set up your paging rules and schedules as well as integrate it with your monitoring solution. We use it with What's Up Gold and it does a wonderful job of making sure that the right people are informed of an outage.

Sometimes if there are multiple alerts in a short amount of time, you can get overwhelmed with notifications and phone calls. I've been in the situation before where when being paged multiple times at once, I couldn't actually acknowledge the pages because my phone kept getting called over and over again for different alerts.

Reliable. We rely on Pager Duty to keep our downtime to a minimum and we've never had complaints with it and PagerDuty itself always seems to up and alerting us in a timely manner. The alert channels are highly customizable and there are enough options to suit anyone's communication style. On top of this, they keep innovating without disrupting the core functionality.

I would like to see more breakdowns and slices in metrics and charts by service, alert type, alert source, etc.

Very reliable (too reliable sometimes) and easy to configure.

Very reliable (too reliable sometimes) and easy to configure. Integrations to large monitoring solutions make it a breeze to setup with other solutions. Mobile app makes responding to alerts even easier than pushing buttons on a phone call.

Wish there were ways to specify certain alerts would only be a text message while others are a phone call per user. Would also like a way to remove users from all schedules at once when needing to remove a user from the portal. Very tedious process of removing them from each schedule individually.

We have been using PagerDuty for more than 6 years. It is a great product in terms of availability of integration, timely alerts, mobile version, ability to select your teams info only, scheduling, and setting up services.

PagerDuty helps in everyday business by providing fast and accurate notifications and alerts for live systems. It has integrations with Slack and email, which helps a lot in notification and resolving incidents collaboratively. The mobile version is a great help as well.

PagerDuty mobile version lucks some essential features that are available on a full version, like scheduling a maintenance window.

Its been great the OOH team knows they wont be woken up for stuff not related to the and we see accurate data. We can manage rotas and shifts much better and its overall improved the perception of the team and their ability out of hours.

The ability to to have the information displayed and on the go with the App is great for us as we can engage with stakeholders and its bought in consistency for out out of hours team on alerting.

The reporting could improve it can give better detail when we are granular on different services but this has improved form when i first used the service.

We use PagerDuty for our on call rota. It was my first experience of such software and I would recommend it to others for its list of features and general ease of use.

Schedules and rotas are easy to set up and administer. Call outs are easy to receive and acknowledge. The app makes it easy to respond to an incident.

The app is a little limited. If a user gets a lot of callouts (e.g. multiple services go down) then I don't know of a "select all" option to ACK. Also I believe that users must go into the web version to administer rotas etc...

Overall it's a great and mostly reliable product

Not having to carry a physical pager, separate phone for being on call The ability to see who's on call when easily Overrides API management of configuration

Lack of an undo feature or revision history It's difficult to configure a business hours rotation without creating a separate set of configuration, it would be nice of the escalation policy section included some time based logic Outages mean missing critical alerts

It solves many of our problems for alerts escalation. I used PagerDuty so far in 3 companies, and it solves many problems.

Web interface is a bit difficult to use. For example: when editing on call schedules — for each edit there's no way to return to previous screen, always I need to go to the top menu, select menu item, another menu item. It can be quite time consuming.

Positive experience with maintaining an on-call rotation so others know who is the priority contact at any time and members of the team can all expect some time off-hours that they can be truly at rest.

Complex scheduling and calendar sharing Multiple vendor integrations user identities

no problems that are likely to be caused by limitations of the service, it is complicated to get right, but works great once it's been properly configured.