External reviews
External reviews are not included in the AWS star rating for the product.
Easy to integrate, hard to live without
What do you like best about the product?
I appreciate the lightweight nature of PagerDuty and the fact that it easily integrates with all of our third-party services like Slack, Datadog, and M/Monit. The Slack integration especially makes it very easy to interact with triggers, and there's even a Hubot integration that allows for easy access to PagerDuty triggering and OnCall information. We've had PagerDuty since nearly the founding of the company, and it has been a pillar of our Operations team and our critical response efforts.
What do you dislike about the product?
Nothing on the fault of PagerDuty, but it's somewhat obnoxious when a monit timeout forces a manual trigger resolution.
What problems is the product solving and how is that benefiting you?
We use Pagerduty for it's basic purpose, to alert on major issues with our running systems, to manage OnCall rotations and to get a hold of OnCall personnel when something is failing. It's been an especially useful metric for our system resilience as well: Good Monitoring + Fewer Alerts = higher resilience.
Recommendations to others considering the product:
If you're looking for a lightweight and integration-rich application for OnCall-rotation management, Systems Alerts, and incident response management, PagerDuty is second-to-none.
- Leave a Comment |
- Mark review as helpful
Perfect Tool for Incident management
What do you like best about the product?
Integrations with external services. For example, Slack, email alerts, etc., Managing the shift schedule and overlapping without changing the original schedule, adding/removing the resources from the schedule, and analytics like ticket handled by each team and each user.
What do you dislike about the product?
Scheduling is quite complex for beginners, once we get to use to it, it will be easy work. To overcome this issue, if you have some video guide, that would be a real help.
Timezone issue on the schedule. For example, one engineer is in the GMT timezone and another engineer is in IST Timezone. But this shift schedule displaying a common timezone for every other location user. I would recommend adding the auto timezone deduction based on the location. And if user changes the timezone, layer is not changing accordingly. It will still show the same time. Let's say there is a layer, that starts from 8:00 am GMT to 1:00 pm GMT. if the user changes the time zone from GMT to IST, the layer also should change as per the IST time zone. Instead, it will still show as 8:00 am IST to 1:00 pm IST. This is a kind of overhead while defining the shift schedule at first.
Timezone issue on the schedule. For example, one engineer is in the GMT timezone and another engineer is in IST Timezone. But this shift schedule displaying a common timezone for every other location user. I would recommend adding the auto timezone deduction based on the location. And if user changes the timezone, layer is not changing accordingly. It will still show the same time. Let's say there is a layer, that starts from 8:00 am GMT to 1:00 pm GMT. if the user changes the time zone from GMT to IST, the layer also should change as per the IST time zone. Instead, it will still show as 8:00 am IST to 1:00 pm IST. This is a kind of overhead while defining the shift schedule at first.
What problems is the product solving and how is that benefiting you?
Reducing the system monitoring effect. Once we integrated with email alerts and slack, we will not miss any incidents. Mostly I have integrated PagerDuty for Teradata related issues. I have linked PagerDuty and Email for Teradata related alerts. And I have integrated with Slack Application. This helps the non-technical business users to raise the pagerDuty ticket with simple command.
Recommendations to others considering the product:
If you are managing 24x7 operations team, dont want to spend time on active monitoring, then PagerDuty is the right choice. If rightly integrate your setup and shift roaster, then your shift will be easier.
Simple, api-driven service for alerting and escalation
What do you like best about the product?
The extensibility through plugins is top-notch
What do you dislike about the product?
The pricing is a bit obtuse, and like many of their competitors, there is a sso-tax
What problems is the product solving and how is that benefiting you?
Having one place to replace someone being on pto/unavailable is crucial
Recommendations to others considering the product:
Start with defining an incident, and who must respond
A must have tool
What do you like best about the product?
PagerDuty has a really simple interface and does its job in an impeccable way. It send alerts via Phone calls, texts, emails or push notifications and can be integrated with many third party tools. We use it mainly with DataDog and AWS, setup was done in minutes and maintenance is practically zero. It's simple enough to be used by non technical people as well. Their Android app is also quite simple and easy to use and doesn't seem to consume a lot of battery and that was a strict requirement for me. Adding a new device/removing a device or add/remove/change notifications is really simple and takes just few minutes. All notifications can be tested to ensure setup is done correctly, to avoid last minute surprises. I've been a PagerDuty user for more than six years and it never let us down, so they managed to make their infrastructure really reliable, as it should be.
What do you dislike about the product?
the only negative experience I had with PagerDuty was when they broken volume override in their Android app for my Samsung S10e. Issue was resolved relatively quickly, but still it was unpleasant to discover I missed some alerts cause of a bug in their app. Anyway, they fixed it and I haven't had any other negative experience with them
What problems is the product solving and how is that benefiting you?
PagerDuty helped us organizing our on-call schedule and it ensures none of the alerts gets unnoticed. We needed a simple and inexpensive tool to achieve that and PagerDuty completely matched our requirements
Recommendations to others considering the product:
if you're looking for a reliable, inexpensive and simple alerting tool, then PagerDuty is what you're looking for
Pretty important tool in our toolbox
What do you like best about the product?
Pagerduty integrates well with the various tools that we use - Cloudwatch, Sentry, Loggly, etc... It's very simple to use and setup. We've built some internal tools around the API to facilitate customization of the schedules, on-call policies, etc...
The post-mortem feature is one that we're hoping to make use of more in the future. The ability to correlate an incident and use the notes / actions from the history will be very useful.
The post-mortem feature is one that we're hoping to make use of more in the future. The ability to correlate an incident and use the notes / actions from the history will be very useful.
What do you dislike about the product?
Historically, the iOS app has been subpar, not allowing for enough customization control. The mobile app period could be a little bit better on both major platforms - it can be a little confusing when you get to the schedules screen for example. Also, some clear indication of which direction to swipe in to ack / resolve an alert would be useful. Essentially just some UX-type improvements would help. The DnD override can be clunky at times, though I imagine that is partially because of the mobile platforms and not entirely under PD's control.
What problems is the product solving and how is that benefiting you?
Visibility and in the moment alerting. We've been able to constantly be aware of what is going on with our platform. From first-time bugs to backed up offline queues to servers running out of IO credits. The Pagerduty app has become a very important tool in our toolbox. Other apps have come and gone - not this one.
No longer are we waiting for our clients or users to let us know that there is an issue with our infrastructure.
No longer are we waiting for our clients or users to let us know that there is an issue with our infrastructure.
Recommendations to others considering the product:
Spend some time setting up your alert policies properly and make sure your escalations and order of alert mediums is well setup. You'll thank yourself at 3am! Aside from that, take the time to understand how you'll be using the product - it can be quite powerful and can be a real difference maker if implemented properly.
Pagerduty sits at the core of our devops systems, and offers superb integration
What do you like best about the product?
I love the ability to route almost any kind of issue or alert to it, from standard cloud services to our in house application software. I think the ability to create flexible escalation paths is superb.
What do you dislike about the product?
I haven't seen anything I truly dislike. It would be useful to have alternative escalation policies for a service, to define different paths for holidays and other scheduling types.
What problems is the product solving and how is that benefiting you?
We provide IoT data ingestion and analysis for enterprise customers, who expect very high uptime. Pagerduty helps us achieve this with a very small development and operations team by keeping us aware of any problems that might arise, but without putting a burden on us to run our own notification and alerting services. Pagerduty keeps my overhead for running and managing operations as low as possible.
Recommendations to others considering the product:
I recommend doing a trial and seeing how easy it is.
Pagerduty good tool for management.
What do you like best about the product?
I like Pagerduty in many aspects, the main one is that it has full availability if we evaluate it in the maximum percentage scale, attracting more attention thanks to the fact that it allows access to the api of its platform for custom configurations in additional ones. terms, it can be mentioned that you acquire an integration system with other compatible platforms in order to guarantee a work in accordance with the web incident management solution in a very agile way.
What do you dislike about the product?
Regarding improvements in some aspects of the system, we could highlight that the user interface is somewhat clumsy, due to the fact that it does not maintain current modernizations, its task management and information that it provides to the client, it may be old and outdated a problem according to its formal bases, from another point of view we can clarify that the price levels and the available functions do not always adjust to one's own essential needs, which makes negotiations difficult.
What problems is the product solving and how is that benefiting you?
Pagerduty is used for incident management and is an integral part of our observability platform in all development teams within our business business, that is, it offers us the monitoring of all our sources of operations for each one of the products generated by my organization, in general all these inspection and alert tools, are used by several of the teams that report through this software, in the same way both for the personnel on duty by different means, and for our clients the status of the platform.
Recommendations to others considering the product:
If you have a large organization with centralized resources and many complex answer cases, Pagerduty could be the best solution for you and your company, as this tool probably has everything you need, as long as you are available to work on it mentioning that she makes it highly recommended thanks to her management of a team's on-call rotation, including the intersection, of specific team members for service that is considered fantastic.
Solid product with good serice and support.
What do you like best about the product?
Supports our operational needs for messaging and is easily managed
What do you dislike about the product?
Nothing significant. It is a solid product
What problems is the product solving and how is that benefiting you?
SMS alerting for service management
Easy API to integrate with
What do you like best about the product?
The API was very easy to integrate with custom applications. Was able to configure web hooks to have PagerDuty send programatic notifications as well. The documentation was very good and the documentation itself has the ability to perform test calls built into it.
What do you dislike about the product?
The mobile app and website offered some differences in features which is understandable. There were a few things that seemed to bypass work flows when done in the mobile app.
What problems is the product solving and how is that benefiting you?
It is used for on-call scheduling and integration with custom applications. The calendar enables anyone to see who is on call and what the full schedule is by service.
Reviewing PD
What do you like best about the product?
I can trust 100% that pages will get sent.
What do you dislike about the product?
Most users first time experience with PagerDuty is that the interface is confusing.
What problems is the product solving and how is that benefiting you?
Send alerts from multiple systems to a rotating cast of on-call people in different teams. This works in a rock-solid way.
showing 231 - 240