Reliable alerting platform to ensure operations continuity
What do you like best about the product?
We've implemented PagerDuty because we needed a way to centralise our alerting workflows in order to improve our incident response. PagerDuty made sense because it was broadly compatible with most of our observability tools (Azure monitor, AWS Cloudwatch and New Relic). It also features a very simple and intuitive interface that makes its set up rather quick and simple. What I like best about PagerDuty is its integration with Microsoft teams which works very well. It also comes with a Ms Teams bot that allows you to summon PagerDuty through direct commands, which makes things quicker since you don't have to log into the UI to perform common actions such as acknowledging or closing triggered alerts.
What do you dislike about the product?
I think the mobile application for IOS is not as good as the web interface, not because its lacking some of the core features but rather because of the way the information is displayed. I believe the layout makes it very cumbersome when you're on-call and have various active schedule assigned at the same time. I would like a cleaner interface on the app with maybe more pictogram to make it more uer friendly.
What problems is the product solving and how is that benefiting you?
The problem PagerDuty has been solving for us is : how do I centralise my alerting workflows that comes from various sources into a single platform and ensure reliable routing to the appropriate incident responder. PagerDuty also make sure no one drop the ball when it come to critical production incident thanks to its escalation policy feature, that allow for redispatch in the absence of ackowledgement.
There are no comments to display