PagerDuty

"Bye Bye to old school on-call practices"

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

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

Inconvénients: 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.

"Pager Duty - Proof you get what you pay for"

Commentaires: We immediately handled the overflow of noise from Nagios, AppDynamics, Dotcom-Monitor, SCOM(from our dc provider) and were able to drop a cellular device using the centralized phone contact with Pager-Duty. We also were able to put our on-call schedule into PagerDuty to realize immediately who was on-call for what product, in what region. There was a very immediate value add realized from even just trialing PagerDuty.

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

Inconvénients: 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.

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

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

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

Inconvénients: 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.

"reliable"

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

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

"Great solution for on-call and incident management for any organisation!"

Commentaires: We have implemented PagerDuty across our SRE and Support organizations and are beginning to roll it out to our engineering teams. This is providing us rapid Incident response and rapid engagement of teams to assist during incidents, no matter what time of day it is or where the teams are geographically located.

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

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