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.

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.

On-call software with rich features

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

Avantages :

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.

Inconvénients :

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.

Immediate Support Team Engagement

Avantages :

I was an IT Lead at the Service Desk when I used this tool most. Being an overnight team member, we needed to engage on-call support whenever we had a widespread issue. Our needed support was pinged appropriately and we received the support we needed thanks to this software.

Inconvénients :

Too many e-mails generated out to support groups

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.