What do you like best about the product?

Getting notified and attending to incidents is not only made easy but also fast.
It connects the right team/person with the right incident for fast response

What do you dislike about the product?

Sometimes ticketing can be overwhelmed. However, it's an overall worthy software

What problems is the product solving and how is that benefiting you?

PagerDuty ensures better coordination of teams and makes it easy to attend to incidents.

What do you like best about the product?

It enhances customer experience
Handles issues in real time
Identify problems and ensures they don't reoccur in future.

What do you dislike about the product?

This tool is not for beginners. Needs experience to use it.

What problems is the product solving and how is that benefiting you?

We use this product to make customer experience better and to identify problems faster for better solutions.

What do you like best about the product?

The tool continues to grow in usefulness and sophistication. Apart from the tool, I most appreciate the expertise in learning from incidents that Jeli brings into your organization when you partner with them.

What do you dislike about the product?

The downsides of Jeli are similar to the downsides of adopting any new tool. It's something else you must learn to use and become familiar with to derive value from. Its not difficult to use but, like anything still takes time. The documentation to enable asynchronus onboarding could be improved.

What problems is the product solving and how is that benefiting you?

Performing incident analysis is a time-consuming process. The jeli tool enable me to analyse an incident quicker and help dirive more profound learnings. The expertise they bring in general approaches to learning from incidents is much into an organisation help encourage a learning culture.

What do you like best about the product?

PagerDuty makes it seamless to attend and resolve incidents like comprehending who is on a call.

What do you dislike about the product?

Ticket time to machine time for incidents was overwhelming during initial setup.

What problems is the product solving and how is that benefiting you?

Automate worl across teams by enhancing coordination business response via dashboards and real-time alerts.

What do you like best about the product?

Am satisfied by how PagerDuty ensures reliability management and automated incidents response.

What do you dislike about the product?

I have not encountered any failure or problem.

What problems is the product solving and how is that benefiting you?

It enables our large team to share on-call load.
Easy customizable and allows many scheduling options.

What do you like best about the product?

It identifies tasks that can perform well with suitable digitization processes. It automates projects across the applications to increase production and enhance achievement of set targets. The machine learning system has streamlined integrations and application orchestration.

What do you dislike about the product?

PagerDuty has all digital tools for upgrading business operation models. There is no showdown on performance from my experience.

What problems is the product solving and how is that benefiting you?

The platform has brought together workforce team and customers to work under same goals. It has streamlined cloud and on-premise services. It solves problems experienced by various teams and mobilize resources to the productive projects.

What do you like best about the product?

***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.

What do you dislike about the product?

***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.

What problems is the product solving and how is that benefiting you?

***EDIT***
Pagerduty provides an intutive method to route alerts based on alert type, severity, required responder and more. It also provides a 0 latency notification service to alert you when a new alert requires attenrtion.

---
They create far more problems than they solve..
We use the product for alerts based on prometheus, emails and integrations (- which suck)

I desperately want to switch to a better solution

What do you like best about the product?

For me, the best way to prevent a service failure from impacting production is to promptly notify and recognize the responsible overarching team. When a problem arises with my project, PagerDuty plays a critical role in alerting the appropriate parties in a timely fashion, which is crucial because my company has a number of projects running in parallel. Moreover, I appreciate how adaptable the system is in terms of the alert configurations we may change at any time. There are several ways to acquire assistance more quickly and improve the quality of service.

What do you dislike about the product?

According to my experience, PagerDuty's UI is not straightforward, and the software's configuration settings might be challenging to master. It might be confusing for a new user to figure out how everything works; when anything goes wrong, they provide you a link to the Splunk logs, but when the instances are shut down, the logs disappear.

What problems is the product solving and how is that benefiting you?

We use synthetic testing to monitor the health of the services we provide to other projects within our business. To do this, we combine S4 Clint's health score computation with honeycomb and transmit the results to PagerDuty.

What do you like best about the product?

Pagerduty is highly scalable and we seamlessly integrate it with a variety of software to better our response time to incidents. It offers us unified particulars on incident occurrence ensuring straightforward response and accuracy during the examination. The finest part of Pagerduty is how prompt alerts are. We are now able to manage on-call schedules in a much more advanced and faster manner. It has a legitimate portal that allows for easy navigation when we are submitting tickets or searching for the latest tickets.

What do you dislike about the product?

I wish there was an option for us to choose when to be paged and when not; it keeps sending alerts even when we aren't available. Pagerduty is continually upgrading and I appreciate that.

What problems is the product solving and how is that benefiting you?

Our way of resolving incidents has improved massively since we deployed Pagerduty. The platform allows us to resolve incidents at a faster rate as it provides a uniform place with all the data about an incident after merging it with different platforms including service now.

What do you like best about the product?

Ui/Ux of the application is effortless on scheduling a call and best part is sending a alert message to the team during critical incident happen.
Pagerduty can be easily setup in each teams and making a alert message for individuals.

What do you dislike about the product?

There is nothing to dislike from pagerduty. Only thing I noticed calender in pagerduty is not a best part it needs some updates, but pagerduty takes feedback from the users and consistenly improving tha app.

What problems is the product solving and how is that benefiting you?

I'm using pagerduty in my team to alert the co workers during any issues occurred in infrastructure level.
It is well integreated with AWS and other clouds services like atlans, etc.