Opiniones de PagerDuty

Bye Bye to old school on-call practices

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

Puntos a favor:

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.

Puntos en contra:

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.

A Modern and Reliable Incident Management Platform - PagerDuty

Comentarios: We have been using PagerDuty for a few months now and have been really pleased with the experience. The incident response capabilities have been invaluable in helping us quickly address any operational issues. The user interface is easy to use and the integration capabilities have been especially helpful. We have experienced a few hiccups with customer support, but otherwise our experience has been positive.

Puntos a favor:

PagerDuty is a modern and reliable incident management platform that has simplified the way our team deals with operational issues. It has an intuitive user interface that makes it easy to navigate and manage all aspects of incident response. It also provides detailed insights on incidents and their root causes, allowing us to quickly identify and address any issues. The integration capabilities have been especially helpful in allowing us to quickly integrate into our existing systems and processes.

Puntos en contra:

The only downside we have encountered with PagerDuty is that the pricing can be somewhat expensive for smaller businesses. Additionally, the customer support could use some improvement, as responses are sometimes slow.

On-call software with rich features

Comentarios: I have been using PagerDuty for 1 year now, and I'm with the product so far. The only negative thing about the PagerDuty is the big latency during the incidents.

Puntos a favor:

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.

Puntos en contra:

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.

Very dependable alerts and notifications service

Puntos a favor:

Pagerduty has been the de facto standard for real-time notifications of on-call engineers in several IT product teams that I’ve worked in. It was easy to set up, integrates well with Slack and notifies the right people reliably and automatically. I really like the flexibly configurable notification rules (for example, send me a push notification first, then if I don’t acknowledge the issue, follow up with a text message, then a phone call, lastly try my personal phone number)

Puntos en contra:

The UI of the PagerDuty dashboard is not very discoverable, making it difficult to learn about many of the advanced features and configuration options

PagerDuty : A solution to almost every problem you didn't know you had yet

Comentarios: The software just works. We have had almost thirty thousand alerts flow through PagerDuty since we first started using it. The software completely replaced a rather broken SMS / Email alert chain overnight and has been by far the most valuable product we have purchased for keeping our system uptime levels where they need to be. Lastly a personal experience which I will always cherish. It's a snowy winter day and you're on call, but you needed paperless, and cat food, and pedlyte and diapers and other bits, so you took your 2 year old to a big box store. You're all the way at the back of the store and your phone goes off with "Something's broken... Something's Broken... It's your Fault! ... It's your Fault!..." In the box store, with a full cart and a toddler. Next thing you know... you're flying through the box store to the front, diapers falling out of the cart, sippy cup lost, toys missing, and toddler singing along with your phone since he now knows the words quite well. Get to the front, abandon the cart, the two children's voices still going full tilt, and get out to the parking lot just in the nick of time to production by ninja resizing a set of boxes as they are almost to the point of falling all over themselves. No one noticed. Thanks to PagerDuty. And now I'm *still* known as "The Something's Broken" dude by the managers of that store. They sing it to me every time I'm there 2 years later.

Puntos a favor:

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.

Puntos en contra:

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.

Helps me sleep at night

Comentarios: PagerDuty keeps my entire team in the loop when something goes wrong with our app. We couldn't deliver the level of service that we do without PagerDuty

Puntos a favor:

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.

Puntos en contra:

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

Pager Duty

Comentarios: Helps monitor critical systems and alerting

Puntos a favor:

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

Puntos en contra:

After a few years the price started to increase.

PagerDuty make it feel more like a pleasure than a Duty

Comentarios: Surprisingly easy to setup rotating schedules, schedule maintenance window exceptions, and have alerts triggered from many sources including email. No one on call can say they didn't hear their phone anymore.. you will be phones, emailed and SMS messaged.. and it will loop until you (or someone else on rotation) knowledges the issue.

Puntos a favor:

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.

Puntos en contra:

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

Ensure High availability of your product to the end user by integrating it with PagerDuty

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

Puntos a favor:

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.

Puntos en contra:

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

Industry standard for managing On-Call Duty Alerts

Comentarios: Great instrument to manage who, when, how will receive the important production alerts

Puntos a favor:

Easy to configure team schedules for on-call personnel, giving the ability to fine-tune critical, high, medium and low level alerts in terms of who, how fast and via which communication channel shall receive the alert.

Puntos en contra:

Honestly - I am happy with PagerDuty and cannot think of something that I didn't like about it so far

An Excellent Service for Orgs with complex alerting needs

Comentarios: PagerDuty has met all of our needs to-date. We reassess vendors regularly, and have yet to try someone else.

Puntos a favor:

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.

Puntos en contra:

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.

Get alerted when your services go down or on urgent mails from the customer, and track it

Comentarios: PagerDuty has continually helped us in identifying the unusual issues and edge cases, now our product is stable, and we ensure high availability of our services , it has been a great experience with it

Puntos a favor:

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

Puntos en contra:

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

Does way more than what is on the box if people knows to use it.

Comentarios: Overall its been amazing and always a friend of operations team now spreading to development teams.

Puntos a favor:

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

Puntos en contra:

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

PagerDuty review

Puntos a favor:

Good customer support, documentation and API

Puntos en contra:

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

Pagerduty is Life Safer for DBA

Comentarios: Overall We are happy with this product from first day as it ease lot of manual intervention for any failure or critical alert which help us to maintain our SLA

Puntos a favor:

Pagerduty is one of the premium product that provides the best oncall features for any organization which is looking less manual ways to manage the escalation, Pagerduty provides web interface along with Mobile app and integration with lot of API's (e.g Slack) which makes this product very useful for Infrastructure,DBA and Help Desk teams.

Puntos en contra:

So far i don't see any noticeable short coming which need to be explored ,i have they will add more features in their mobile app along with little bit more stability as sometime their mobile app crashes on Andriod.

Good On Call Platform

Comentarios: Easy implementation, good support

Puntos a favor:

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

Puntos en contra:

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.

It is hard to beat PagerDuty for the functionality and itegration into alerting systems

Comentarios: On-call rotations are managed through PagerDuty and it allows each functional area to build their own escalation procedures. We are exploring the newly added teams and business process functionality of the software to improve collaborative efforts between teams.

Puntos a favor:

Lots of Integrations with other tools and ways to integrate even without commercial integrations, with RESTful interfaces and email integrations.

Puntos en contra:

Working with the software renewal and licensing aspects of the software has been challenging. There were some legal snafu's that made getting the agreement signed quite a chore.

One of those products that solves one key problem really well

Puntos a favor:

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.

Puntos en contra:

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

Review about PagerDuty, from a user standpoint

Comentarios: Over all as I said it does the job. Minor UI improvements will help to make it more convenient.

Puntos a favor:

First of all, PD does the job. It means that my company can customize it as they wish, and I get alerts efficiently using email, SMS and phone calls (and the app). The alerts are effective and the needed information is found inside the incident body. It is not trivial to have a system that works in large scale as it does in Taboola.

Puntos en contra:

There are some end-user UI issues I would like to raise: 1. It is too easy for me to see others' incidents. I do not want to see it - it's confusing. Once I actually closed an incident of another person, mistakenly. Yes it was my mistake and perhaps my IT department's configuration mistake, but the UI shows me these incidents. I am only interested in mine. 2. In "alerts" I see many alerts which are not mine! again you are loading me with details not relevant for me. 3. In "indicents" in the website, I put on "any status" but I don't see closed incidents. 4. The smartphone app is great, very focused to what I need. Why not add the option to add a calendar entry for PD on-call shifts?

Best in breed incident and on call management

Comentarios: Pagerduty is an excellent tool to enable on-call teams to response to and collaborate on operational issues with ease. The wealth of integrations with other popular tooling make it the go to option for many people.

Puntos a favor:

Quick to implement and scale and it helps the organization to respond to and resolve incidents in a timely and effective manner. Features such as real-time alerts, on-call scheduling, and incident tracking and reporting are excellent.

Puntos en contra:

The cost model can be a little confusing and/or opaque. The reporting module, in my opinion, should be included with the base product

Solid solution for on call devops

Puntos a favor:

Pager Duty overall is a great solution for handling on call escalations for server and environment issues. It makes it easy to integrate with third part solutions to generate actionable alerts for on call engineers. If you are using a product that doesn't natively integrate with Pager Duty (which is rare), you can use their email integration to submit issues that way.

Puntos en contra:

The interface for adjusting the on call schedule could be improved - when updating a schedule to cover an engineer while they are on vacation, it can be really confusing to setup.

Does What It Says On The Tin, And Very Well

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

Puntos a favor:

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.

Puntos en contra:

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

Beep Boop

Comentarios: Overall it's a great and mostly reliable product

Puntos a favor:

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

Puntos en contra:

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

Making sure you're up in the middle of the night

Puntos a favor:

While not super easy to setup, it's generally a one time things. Once you've configured PagerDuty you're free to explore all the integrations available. We use it connected to our AWS monitoring, DataDog, Rollbar and bunch of custom integrations. PagerDuty also helped us reduce to amount of alerts - it's easy to go to far, and being woken up in the middle of the night for something completely irrelevant helps you make better decisions about platform monitoring.

Puntos en contra:

Not all the escalation rules are clear. Editing schedules could be easier - if you do that on a one-off basis it's usually by trial and error.

Essential part of the support stack

Puntos a favor:

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.

Puntos en contra:

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.