Avaliações do PagerDuty

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.

Integration with CloudWatch, webhooks, Jira is outstanding, functional, and reliable. The application has gotten better over the years I have used it.

Handles real issues in real time with everything you need

Allows on-call individuals to customize their notification scheme to fit their life. Having full control over when, where and how you are "dinged" is just awesome.

It's a little expensive per user if you need simple API things. The rule set for routing isn't as good as VictorOps for the same price point.

PagerDuty is missing a "default route" option like VictorOps has. This is minor, because it's rather trivial to setup an extra account and use that "extra dummy account" as the "Default". I'm counting this as a "con" since we have had to do this for every single deployment of PagerDuty I've worked on where we wish to have alerts go to a team, but not actually notify anyone.

Lastly, business-hours-only alerting is a little weak. (Maybe it has gotten better.) Every implementation I've found, we need to have some sort of queued' alerts which we don't want to wake us up in the middle of the night but we want to or need to know about next business day situation we have had to work hard to implement in PagerDuty.

PagerDuty does the job. It's gonna wake you up in the middle of the night, no matter what. The number of ways they are providing for acknowledging an incident is great. You can get a call, an SMS message, a push notification on the browser, or a mobile notification for an incident.

PagerDuty has some latency when it comes to acknowledging incidents. After acknowledging an incident by using the mobile app, getting an additional phone call about the incident is a little bit annoying.

PagerDuty is very important in projects that deal with tickets, incidents, and tasks that are bound by service level agreements. This is the case in all the 24*7 projects. The PagerDuty administrator can allot different severity tickets to the PagerDuty and specify the method by which the users can be notified about the same. The PagerDuty provides different ways of notifying the user: Via email, SMS, or call. The best thing about this software is that if the user does not respond to the ticket on the PagerDuty portal within a specified time, it will send the user an SMS. Then, if the user still is unresponsive to the ticket, a call will alert the user to work on it. This process ensures that high criticality tickets are not missed. In this way, SLA breaches are avoided and so are escalations.

There are no major drawbacks to using PagerDuty since it is very useful software. But, at times when there are multiple administrators handling the software, if one administrator makes changes to the setting of the software, the other administrators might not be notified of the changes. This might cause a confusion between the users and the alerting process.

PagerDuty very easy to configure and use, I've given access to team leads with no instructions and they've been up and running that day.

It'd be great if PagerDuty could integrate with all versions of Jira natively without a 3rd party plugin.

I love that Pagerduty has integrations with all of the application monitoring tools that we use. If anything starts to act up, Pagerduty makes sure we are aware of it.

Nothing really. The pricing is fair, the reliability is flawless.

The alerting, even when you turn the volume down on your phone if an alerts triggers the volume will get turned back up for that alarm

After a few years the price started to increase.

Easy to setup.
Trigger alerts via emails.
Good interface.
Integrates easily with MS Teams.
Rotating schedules for multiple team members.
Easy to make schedule exceptions.
Easy to acknowledge alerts via email, phone, app or SMS.

I can't really think of any Cons.
I really enjoyed getting this setup and benefiting from the easy alerts.

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

The mobile app is one of the best features of PagerDuty.

We have not yet found a feature of PagerDuty that we don't like.

I tried a competitor's product which was a free notification manager up to 11 people. It took me 3 days to get anywhere with a basic task of integrating 3 of our noisiest alerts. Then I tried the PagerDuty trial and got 2 of our noisiest alerts built out in 1 day. I added 3 more over the next 2 days to go well over the targeted mark. Coworkers were excited to help put time and effort into the system as opposed to the free tool which I couldn't seem to get any traction with. The alerts were immediately available, they were easy to get posting to my cell phone, and adding additional users was a cinch. The tool unfolds and becomes more useful the more time you put into it where some tools you struggle to get right and then you're afraid to make changes.

The UI is a bit quirky in the scheduler which is a pretty important view if you have a rotating on-call shift you're trying to tie down. There was a lot of "can't delete before you delete elsewhere" scenarios where there could have been a "will also delete these elsewhere, are you sure?" scenarios. What you gain in ease of use and stability in the mobile platform you lose in overall functionality, it is simple almost to a fault and while it seems silly there's no skinning of the mobile app to better suit your personality in a hyper-customized world. I'll know shortly if they're willing to go longer but they seem to be sticklers for the exact trial length + only a little. Corporations interested in putting in a full month long or longer trial that may need that amount of time to show value, create a SOW, and have a PO issued may be stuck in limbo for a few weeks.

- The flow of events, mainly. How it goes from Triggered, to ACK, to resolved with snooze options, it feels natural.
- Notification flow: How I can set up to notify my phone, wait two minutes before texting me, and wait five minutes before calling me.
- Slack integration

- Configuration can use some redesign. Its hard to find some settings sometimes. I told a coworker about updating notifications, and it took them a while to figure out where they can do that.
- Some important features are hidden behind a higher tier plan, eg: analytics.

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.

- 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

PagerDuty has an incredible featureset that spans just about every "on call" use case you could dream up. They highlight new use cases regularly in blog posts and Account Management is pretty solid.

Pricing is far higher than competitors which makes it a tough pill to swallow with annual billing. There's not much focus on controlling costs and very little leniency on things like prorating user seats if we have a new hire (it appears to be billed as a full month). With the highest price point in the industry, Account Managers usually have leniency to retain customers by avoiding these nickel-and-dime approaches to billing.

Simple to use intuitive interface via web and smartphone app, third party integrations with Nagios, Slack, and Atlassian products (Jira), as well as custom webhooks for use with monitoring tools (grafana). Overrides available for scheduled rotations. Custom alert sounds was a nice touch.

Attention from customer support requires being a larger customer paying a significant amount of money. Which we were when I used and configured this, and it worked well for us.

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.

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

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.

Application is amazing, simple interface, notifications are delivered right on time, sound notification works amazing, so it doesn’t matter day or night time you will know everything what is going on, no matter where you’re at. The size of the application on your mobile device is tiny compare to other similar applications, but it provides you with all the necessary features for 24/7 support. Integration with Jira works amazing, no problems at all. Price is lower compare to similar products.

It is missing night mode feature on web version and it is difficult to view the screen at night, on the other hand mobile application has it. It would be also great to have a chance to place different sound notifications on different Incidents. Also mobile application is missing face id or any other security log in recognition.

- 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.

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

I like that we can easily resolve through the app.

I don't like that we can only have 3 users.

Good customer support, documentation and API

Lack of filtering/search options. Not possible to search for specific alerts without the use of the API. It's a pain.

No audit logs to see who made changes and what the changes are. Lack of features in the PagerDuty slack plug-in as compared to other alternatives such as OpsGenie

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.