PagerDuty Reviews & Product Details

I like how pager duty sets up conventions for handling incidents, and the way they expose information to users. In terms of support, it's a relief having a tool like this producing alerts for our services. It integrates out of the box very well with the most recent telemetry tools, and its UI is very intuitive and easy to use. Review collected by and hosted on G2.com.

The only improvement I can suggest to PagerDuty UI is a slight improvement in the notes. When acknowledging and troubleshooting an alert it would be useful to tag other people in the notes. The ability to add screenshots would be a plus. Review collected by and hosted on G2.com.

***EDIT***

Customizeable routing, both at the global top level and at the individual service level. Custom alerting behavior per service and given logic.

Intuitive OnCall scheduling and escalation policy.

---

PagerDuty is well spread and used by many - though I find less than 0 reasons why..

Other than the fact it is working somewhat as expected (and that also isn't easy to achieve) there's not a single good thing I can say about this product, or the team developing it. Review collected by and hosted on G2.com.

***EDIT***

Original below.

When a good word is due then one must be given. Kudos to the PagerDuty team for making a great turnaround comback with their product.

It now works as a whole ecosystem wiht integrations and fully customizeable logic in terms of routing and alerting conditions. All the below mentioned was fixed to the point where not only is the product usable and somewhat intuitive, but also provides unmatched capabilities at a very low implementational cost (simple to integrate with).

it now comes with a fully functional Terraform provider as well!

Good job PagerDuty engineering for making the biggest turnaround I've seen, And thank you for taking this matter seriously. It did not go unnoticed.

------

EVERYTHING. I'll explain:

1. The product is bad(!), and their code is not up-to-standard with current methodologies (SSO is only partially supported, alert ingestion and processing is lacking, etc'). It also looks like a "dot com" era product written in basic HTML1 and PHP - but that's a matter of personal opinion and preferance..

2. Everything is confusing - integrations can be set on the global level and would not appear on the service level, and vise-versa, there are multiple locations for setting alert handling rules and above all - the docs are outdated and contradicting

3. Bad organizational behavior - for example, they do not have an SLA for support tickets. My tickets usually go about a week unattended. Also, they removed Support Chat for non-premium customers without giving notice. As far as I understand - my tickets opened via chat are GONE. No notification, no nothing. Also, our account managers are away constantly and rarely answer messages.

4. Product has A LOT of design bugs - one example is that even when using SSO - deleted users are not EPHERMAL!!!! meaning, that when you remove a user, the user object remains!!! (a perfect example of such a case is when setting a user as onCall, and then removing it, the deleted user remains as oncall - WTF?!?)

5. And worst of all, they have a terrible attitude!! - I got the sense that they truly believe in their right of way. No regard for customers, no regard for the operations dependent on their product, and zero f***s given about the customer. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

As the title suggests, PagerDuty is very effectively built in such a way that it doesn't delay alerting on-calls and leadership of incident. Yet nobody wants to get any PD alerts xD. PagerDuty is easy to use which we use on regular basis for reports, retros, etc. Review collected by and hosted on G2.com.

Again as said, alerting of any issue is something everyone dislikes - lol. However, I find PD as a very efficient tool for any kind of alerting from any datasource (such as grafana, coralogix, Last9, etc) Review collected by and hosted on G2.com.

Esclation policies , How it group together incident and reduce noise Review collected by and hosted on G2.com.

MOst features are now add-on which makes it difficult to convince managemnt to buy. Review collected by and hosted on G2.com.

1. PagerDuty is most suited for highly critical business application or server to monitor the application and server alerts.

2. Alerts are automated, meaning it can send alerts to multiple channels.

3. The company that I worked for used PagerDuty extensively, which helped in on-call scheduling and incident Management Review collected by and hosted on G2.com.

Since PagerDuty is well established in the market, it's cost is comparitively higher compare to other Incident Management providers.

I personally did not like the bombarding of alerts for the issue, howerver this can be silenced now with snoozing the alert. Review collected by and hosted on G2.com.

Pagerduty is SaaS based alerting systems allowing companies to use for their in house technology for incident response. It provides the real-time monitoring for all the infrastructure and services by generating calls and emails as needed. It also provides a lot of integrations with other products for example Jira, Nagios and Slack. PagerDuty has a level of escalation setup that allows incidents to follow a process chain which benefits a lot in escalation matrix. PagerDuty features like SSO, Role based Access are really a good add-ons which ease our usage and aslo initial setup. Review collected by and hosted on G2.com.

Pagerduty is expensive as compared to its competitors in the market and Its integration lacks some features like easy set up. It has a way to improve its configurations so that a user with zero technical knowledge can understand it. Auto-recovery of alert feature sometime fails and it needs some improvements. Review collected by and hosted on G2.com.

- It's easy to schedule oncall alerts between different teams and for different channels.

- It has incident management so it becomes one stop to handle the alerts the right way

- It's flexible and provides options to receive/manage alerts during work hours and off hours Review collected by and hosted on G2.com.

From what I have used, I couldn't find anything that I dislike. Review collected by and hosted on G2.com.

Pagerduty helps to manage the incident which we can integrate on cloud artichture and other monitoring tools like senty Review collected by and hosted on G2.com.

The support for the pagerduty is less and the pricing is high Review collected by and hosted on G2.com.

1. Integration with our existing tools

2. Customizable on-call schedule and escalation policies 3. Mobile app - helps stay connected on the go Review collected by and hosted on G2.com.

1. Complexity of initial set-up

2. Pricing 3. Not a very user-friendly UI Review collected by and hosted on G2.com.