PagerDuty

Vantagens

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.

Desvantagens

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.

Vantagens

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.

Desvantagens

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.

Vantagens

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.

Desvantagens

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.

Vantagens

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.

Desvantagens

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.

Vantagens

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.

Desvantagens

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