External reviews
External reviews are not included in the AWS star rating for the product.
Pagerduty never fails to get your attention
What do you like best about the product?
Ever since we started using pagerduty, escalations have stopped being a challenge.
What do you dislike about the product?
Email alert rules are a bit simplistic. I'd love the ability to create advanced notification rules based on email subjects.
What problems is the product solving and how is that benefiting you?
We use it for on-call scheduling and alert escalation to engineering teams.
- Leave a Comment |
- Mark review as helpful
Pager Duty from the perspective of a small IT team
What do you like best about the product?
I like the flexibility of the pager duty platform, It's able to connect to various different platforms of ours.
What do you dislike about the product?
Honestly, I've yet to uncover a feature that I sincerely dislike on the pager duty platform.
What problems is the product solving and how is that benefiting you?
We are a small IT team that doesn't have a deep bench to be staffed 24/7, pager duty allows us to get notified of critical incidents over night and leave the less mission critical ones to the morning.
PagerDuty
What do you like best about the product?
It is very easy to get started. The basics work properly and as you become more familiar you have considerable options for alarm management.
What do you dislike about the product?
I personally did not find any dislikes based on our deployment.
What problems is the product solving and how is that benefiting you?
We are using PagerDuty with our Vaonet Portal to provide alerts to support personnel.
Recommendations to others considering the product:
Ease the pain of handling notifications and escalations.
Great tool for tech engagement
What do you like best about the product?
The phone integration is really what makes this product great. Allows out alerting to quickly engage our tech resources
What do you dislike about the product?
Wish there were more product integrations.
What problems is the product solving and how is that benefiting you?
Tech engagement was ensure with the phone paging method.
Part of a well-balanced incident response architecture
What do you like best about the product?
Extensibility with other platforms makes it easy to use PagerDuty as a single-source of information during incidents which leads to faster time to recovery and more accurate post-mortem reviews.
What do you dislike about the product?
At times, the UI has been difficult to navigate. Sometimes something simple like "remove this user" would prompt you to take action elsewhere first, which would lead to another prompt to take action in yet another place first. I believe some of these UX experiences have been improved lately (e.g., by removing a user you're simply told where that user exists within schedules, allowing you to clean it up later instead of being forced to hunt around) but those types of experiences seem like they'd have been discovered early on in UX testing.
What problems is the product solving and how is that benefiting you?
We use PagerDuty to summon people for emergencies, send automated issues to phones based on criteria and severity, and tie reporting into our availability review.
Good support scheduling
What do you like best about the product?
Scheduling of support by group and department. Integrates well with a wide variety of systems
What do you dislike about the product?
Has incident management and other services but some are additional addons.
What problems is the product solving and how is that benefiting you?
Scheduling of team for supporting services
A required tool for a 24/7 operations/support team
What do you like best about the product?
Probably the most important third party tool we leverage.
Handles real issues with ease, sometimes making us forget how critical of a service it is.
The flow of events is crystal clear allowing users of the service to have no issues with understanding what is expected of them (acknowledge, triage, resolve).
Working on a team that supports all backend engineering for a major application that is used by millions of users can be stressful, but we have peace of mind knowing PagerDuty is always resilient and alerting when we need it to.
Having rules in place to auto-resolve issues is crucial.
Snoozing is vital to when there is an issue that does not have a resolution pending.
Definitely how simple it is to get users set up and embedded into the team/schedule/escalation policy.
The simplicity of integrating with AWS, NewRelic, Slack which are all important applications/services we leverage every day.
The analytics reports are so valuable and simple to export.
Handles real issues with ease, sometimes making us forget how critical of a service it is.
The flow of events is crystal clear allowing users of the service to have no issues with understanding what is expected of them (acknowledge, triage, resolve).
Working on a team that supports all backend engineering for a major application that is used by millions of users can be stressful, but we have peace of mind knowing PagerDuty is always resilient and alerting when we need it to.
Having rules in place to auto-resolve issues is crucial.
Snoozing is vital to when there is an issue that does not have a resolution pending.
Definitely how simple it is to get users set up and embedded into the team/schedule/escalation policy.
The simplicity of integrating with AWS, NewRelic, Slack which are all important applications/services we leverage every day.
The analytics reports are so valuable and simple to export.
What do you dislike about the product?
The fact that the PagerDuty Service features can't be intertwined with the Escalation Policy. Just feels like an unnecessary extra configuration.
I wish the mobile app was a little clearer in showing incidents that are high urgency, perhaps bolder font or a label.
The analytics section is a bit clunky and there could be a lot of grooming there to clean up unnecessary data that I don't think there is a valid use case for.
The analytics section sometimes fails to export or does not filter appropriately.
It would be cool if the analytics report could contain graphs or visuals.
I wish the resolution notes had more built around that feature. It would be cool if they went to a centralized place and could be collated.
Sometimes its hard to find certain features or settings, the most recent redesign makes some things hidden that weren't prior.
I wish the mobile app was a little clearer in showing incidents that are high urgency, perhaps bolder font or a label.
The analytics section is a bit clunky and there could be a lot of grooming there to clean up unnecessary data that I don't think there is a valid use case for.
The analytics section sometimes fails to export or does not filter appropriately.
It would be cool if the analytics report could contain graphs or visuals.
I wish the resolution notes had more built around that feature. It would be cool if they went to a centralized place and could be collated.
Sometimes its hard to find certain features or settings, the most recent redesign makes some things hidden that weren't prior.
What problems is the product solving and how is that benefiting you?
Ensures team cohesion and allows everyone to be in the know of status with a few simple clicks of a button.
We are able to work in a unified manner across 3 timezones and over 10 different backend engineering teams.
Responding to incidents more effectively and efficiently.
Reducing redundant areas of troubleshooting, centralizing our flow of AWS -> PagerDuty -> Slack
We are able to work in a unified manner across 3 timezones and over 10 different backend engineering teams.
Responding to incidents more effectively and efficiently.
Reducing redundant areas of troubleshooting, centralizing our flow of AWS -> PagerDuty -> Slack
No more forgetting to rotate oncall
What do you like best about the product?
I like the accountability of acknowledgement and marking resolved.
I like the automated scheduling so there's no more "Who's going to sign up for this weekend"
I also enjoy the variety of service integration options.
I like the automated scheduling so there's no more "Who's going to sign up for this weekend"
I also enjoy the variety of service integration options.
What do you dislike about the product?
Above a smaller user count it can get a little expensive.
What problems is the product solving and how is that benefiting you?
We use pagerduty to automate and add consistency to our oncall process
Definitely will recommend the PagerDuty to friends or colleagues!
What do you like best about the product?
The product's seamless experience is the best thing.
What do you dislike about the product?
I do not recollect anything that I did not like.
What problems is the product solving and how is that benefiting you?
We use the Pagerduty for alerting us when the product goes offline or unresponsive.
We use it to monitor our platform infrastructure
What do you like best about the product?
I found log integration really useful along with AWS integration makes metrics and monitoring really easy
What do you dislike about the product?
Dashboards creation is always a bit complex when you have different environments: production, staging, etc...
What problems is the product solving and how is that benefiting you?
Infrastructure monitoring with escalation policies, the benefit is the integration with our application logs help us to identify problems in a short time
showing 201 - 210