PagerDuty Operations Cloud
PagerDutyExternal reviews
914 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Pagerduty is the Cadillac of Incident notifications
What do you like best about the product?
The API! We were able to set up web hooks quick.
What do you dislike about the product?
The price - we need it to be a Toyota and it ends up costing a ferrari
What problems is the product solving and how is that benefiting you?
data retention for price comparable to S3.
Recommendations to others considering the product:
Truly look at the budget first.
Safeguard for our system
What do you like best about the product?
PagerDuty is an efficient way of doing the alerting when it is required to collect the data from a few sources and notify only the relevant persons via the means those people prefer.
What do you dislike about the product?
Sometimes, it feels like PagerDuty is meant for big corporations with many teams/departments where the incident process is complicated. Building something really simple is not possible or obvious and requires thinking of the play scenarios in the terms of a big company.
What problems is the product solving and how is that benefiting you?
Pagerduty provides a vital part for our system making a bridge between automated monitoring and us humans. Being a small company, we could not afford having a dedicated team of Operations who keeps an eye on the system. Instead, we invested some time building several layers of monitors that all are integrated into Pagerduty. PagerDuty then do the rest---Collects the alerting data and notifies only the relevant people giving them the relevant data to react.
Great tool for incident management
What do you like best about the product?
1. Easy to get support on your products and manage the support schedule
2. Incident analysis and looking back for product improvements on MTTR, MTBF etc is nice
2. Incident analysis and looking back for product improvements on MTTR, MTBF etc is nice
What do you dislike about the product?
The scheduling logic sometimes gets too hard to debug, esp if there are conflicts. The UI does not alert on conflicts very well
What problems is the product solving and how is that benefiting you?
Since pagerduty, it's become a single tool for support management
Day to day user
What do you like best about the product?
It always gets you up with multiple levels of alarms
What do you dislike about the product?
Not being flexible enough about email rules, not being able to connect multiple incidents to anither
What problems is the product solving and how is that benefiting you?
Help desk/ monitoring notification
Wakes me up at night
What do you like best about the product?
PagerDuty reliably and consistently notifies me of events within our infrastructure.
What do you dislike about the product?
It wakes me up reliably and consistently about events within our infrastructure.
What problems is the product solving and how is that benefiting you?
Prior to PagerDuty, we had text message alerts that didn't work as well or as fine grained as PagerDuty.
Pager Duty Does What It Says It Will
What do you like best about the product?
The able to integrate with various platforms.
What do you dislike about the product?
Right now I get 4-5 alerts for the same incident; would love for that bug to be resolved!
What problems is the product solving and how is that benefiting you?
Incident management; we've been able to respond in a timely manner and make sure the correct people are involved in incident resolution.
Overall not bad
What do you like best about the product?
It works as intended, sends messages and calls until it gets a response. The escalation strategy works and while it isn't the clearest web UI, it is possible to see a dashboard view.
What do you dislike about the product?
The web UI can be confusing, and it alerts on recovery messages from our monitoring too (which may be an implementation issue more than a product one). The only other issue we had was setting up a user to be the financial person who owns the credit card info etc - that cannot be done via the web, it needs to be a phone call. For a company of its size, I would have expected a proper role for that.
What problems is the product solving and how is that benefiting you?
24/7 support calls for web services triggered by our monitoring.
Recommendations to others considering the product:
It works, it calls, messages etc. We have not used it beyond that functionality, but it works well and can be triggered easily by our data center monitoring.
Issues with the App
What do you like best about the product?
I like the whole concept of integrating alerts to your phone + app.
What do you dislike about the product?
Usability, if there's a burst of alerts it's hard to snooze them in batch. There is "Select Incidents" option but it's too hard to handle while driving. Obviously, if you are driving, it should have an auto-snooze option, which gets voided after sometime.
What problems is the product solving and how is that benefiting you?
A whole bunch of things from:
System liveliness
System progress(like a pipeline of events handled by an event handler)
Host metrics(Load, up/down)
System liveliness
System progress(like a pipeline of events handled by an event handler)
Host metrics(Load, up/down)
Great for app monitoring
What do you like best about the product?
It works, integrations are easy. Very reliable.
What do you dislike about the product?
Organization can be a little tricky. The concept of teams and services can be confusing.
What problems is the product solving and how is that benefiting you?
We reduce downtime and are able to reliably schedule on calls
Recommendations to others considering the product:
its great
an okay tool for handling pager in your organization
What do you like best about the product?
The basic functionality of getting alerted, and the integration with slack etc.
What do you dislike about the product?
The UI functionality. The analytics on incidents are often time-out.
What problems is the product solving and how is that benefiting you?
UI improvements on scheduling, analytics, etc. are needed.
showing 31 - 40