Avis clients sur PagerDuty

teams can manage their own schedules, including flexible overrides when they need someone else to cover. lot of notification/escalation options, and for each user they can specify how they prefer to be communicated with.

adding users to an existing schedule can cause unexpected issues if you are not careful. also I sure wish that pagerduty app was able to override do not disturb settings on my phone, would love to be able to disable calls and other notifications but still get my PD alerts when I go to bed!

-multiple integrations with many tools.
-easy to set up and use
-mobile App
-stable

Some of the integrations, at least at the moment, are not ways. Such as Zendesk and PagerDuty where you can only create incidents when a Zendesk case is created but not the other way around.
The mobile App does not have all the features as the web platform.

The mobile application works very well
Incident handling and reporting works very well

The administration portal schedule is very confusing and hard to set up for global workflows

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)

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.

Extremely reliable, gets out of your way, lots of integrations

Confusing why there are schedules, teams, rotations etc. too much burden and it’s not simplistic to setup for first time use. Setting overrides and viewing on call schedule should be at the forefront. Should have out of office integration

I really like its incident reporting feature and integration. It is very easy to integrate any system with Pagerduty. Apart from its email, it can notify in other communication platforms as well, which makes it very convenient to browse through its history and configure custom alerts.

It's alerting feature is good and it can alert immediately. At times we receive alerts due to transient failure which could be ignored. So It will be great if we could have aggregate and process the datapoints before sending notification.

This tool makes monitoring so much easier by bringing everything into one place.
Easy to use, easy to set up, and already integrated into a lot of existing tools.
Notification preferences, and schedules, and escalation policies make life SO much better!

The terminology is a little hard to wrap your head around.
Has elements that are dependent on others and makes it hard to clean up after you have already set it up.

We have been using PagerDuty for years for incident management and it has been a key part of our business. We mainly use the notifications and incident escalation side which automatically adjusts to the on call schedules we set.

We haven't anything bad to say about the product as it does everything we need and does it very well.

PagerDuty checks every box I need for notification and incident management.

The only issue I've found is that sometime the push notifications to the mobile App can be slower than emails.

You can use pager duty for different purpose to get alerted and track the alert till the alert was addressed,
we use it for the alert on service down and failures, so that the product issue can be addressed and fixed at the earliest,

Pagerduty serves this purpose good, it alerts in different mediums and at different levels, and there is a rotation policy, if a level 1 user dose not addresses then it alerts the level 2 user and this rotation gos on till the issue is properly addressed, and there are good features like time tracking, historic analysis , team groping, different alert policies, scheduling the users to be on call, snoozing the alert, escalating to other user, etc

some times the web UI becomes slow, the app version dose not have all the features that the web version has

- Setting up override is 30 seconds task.
- Reminder of when Im going on-call and my own notification settings is a life saviour.
- Slack integration
- Api integration
- Postmortems made easier.
- ITIL followed in the core in an automated fashion making incident management a cake walk.

- No way to export the schedule to excel. Only option is to do a calendar export. Which is not what a team lead or manager will want to do payroll.
- Would be nicer to have billing based on number of schedules/services rather than number of users as we are in a devops world where all need to be able to login/resolve alerts. This forces teams to limit access taking them away from being "devops".
- I am not a big fan of the schedule UI. It will be nicer to have days separated with lines on the rota.
- In general the amount of invested on this tool is very minimal by a user, so it is worth simplifying schedules and services for people to understand it easier. The word service itself is misleading for the users.

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!

PagerDuty lets us centralize our notifications, with a good and reliable degree of user control over how pages are delivered. It integrates well with a vast panoply of other services. PD is reliable on iOS, Android, and via SMS and phone.

Managing calendars via the web UI is phenomenally hard, especially for modeling rotations of any complexity. For instance: we do a primary/secondary incident command rotation, in which the secondary handles day-time on-call and the primary handles off-hours. Currently, this requires us to model four different escalation policies, which would be horribly complex to manage *without* having teams in three time zones, which we do.

We also suffer during outages for the lack of a "acknowledge all incoming pages" button. As an incident commander, when I'm trying to manage comms around incidents and system failures, having to *also* manage a pager going off every sixty seconds is, at best, horrendous. We badly need a "current status, open incident" that auto-acks whatever comes in and, say, converts them to summary push-notifications or some other "just an FYI, this other stuff happened" digest.

The thing I like most about Pagerduty is how easy it is to set-up, get working, and consistently be reliable to send alerts at proper times. These things made it easy for us to integrate into our software using their API.

It is a bit pricey, especially if you don't plan on using all of the functionality and features that PagerDuty. For us, PagerDuty was overkill for the kind of alert/messaging system we were looking for so we were paying extra for these features we weren't using. Secondly, the alert/messaging system feels pretty robotic and is not very customizable. It feels like Pagerduty was built for engineers thought it could be used in other sectors.

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.

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.

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.

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.

Easy to go live and setup. As soon as the account is set up, the configuration of services was really easy to setup. We've integrated PagerDuty with our existing Dynatrace platform, and the monitoring and alerts are very accurate.

As this a user-based subscription, we're quite limited to make a group or shared account. It'd be great if there's flexibility in having more users to the account.

1) Alerts for all kinds of incidents
2) Integration with most of the common and popular monitoring and tech sites
3) Easy-to-use scheduler

Pricing (its value over cost depends on the potential revenue loss for your business)

The intuitive user interface along with the supported apps on all other platforms really help in keeping track of events. Moreover PagerDuty has never been down which really speaks a lot about the effort that goes in to making this amazing piece of software

I cannot subscribe to a specific type of pager, or pagers which should get escalated to only me instead of the on-call person.

PagerDuty is a simple but critical piece of our monitoring and support solution. We use it for two purposes, sending alerts to support when urgent customer requests come in, and sending alerts to engineering / SRE teams when something is wrong with our SaaS. It's easy to define the hierarchy of how the alerts should cascade. Integration is simple since PagerDuty supports many common platforms like BambooHR and OneLogin. Oneboarding process is straightforward and simple.

For colleagues in some regions, PagerDuty requires VPN to access which can be somewhat inconvenient. However that's more a reflection of the region versus PagerDuty. Pricing for the highest tier is expensive.

- Easy Integrations
- Simple User Interface, very easy to navigate
- Lots of features and functionalities
- Very easy to setup
- Schedule creation and setting up rotation

Pagerduty is definitely the leader in this space, but it is fairly expensive and hence we have started looking at other options.

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.