PagerDuty vs. sendQuick onCloud

The best features of PagerDuty Operations Cloud are that it is a fairly good tool for alerting. Here is how the process works: suppose there is an XYZ server in my environment hosting a production or development application, and a primary on-call engineer has been assigned for that particular week. We have set up monitoring and observability for that node so that if the node is not reachable, an alert is triggered and sends a notification to our integrated Slack channels with PagerDuty Operations Cloud. If the engineer is available, they can acknowledge the alert. If they fail to acknowledge it, the system calls them on their provided number. If that is also not acknowledged, it sends a text message. If those actions are not acknowledged, it sends an alert to the secondary engineer and calls them as well. This multi-channel approach makes it very difficult to miss an important alert or update. PagerDuty Operations Cloud handles this process perfectly, and we do not miss any alerts because of this system.Regarding the stability of PagerDuty Operations Cloud, I cannot recall an incident where it was not available. I can say that it is 100 percent reliable for my needs.

Incentivized

• PagerDuty sends the alerts set on high severity incidents on time and never misses any single instance.
• PagerDuty help to send alert to mobile calls and Team channel for outage.
• PagerDuty also resolves some of the high severity incidents as part of self healing mechanism.

Incentivized

• From what I have observed, I say customization of notification and alert prioritization are the areas where PagerDuty can be improved. As in our collections team, we also deal with high priority accounts and lower priority system flags, PagerDuty definitely sends the alert, however this sometimes becomes messy. For ex, we had to spend extra time to create multiple escalations and test them in order to handle the priority accounts at first, then others, and that too without overwhelming our team with lower priority notifications.
• I would highly recommend PagerDuty if it begins to offer something more intuitive, premium templates.... otherwise it's a great tool, I would say.

Incentivized

They have been rock solid for us thus far and are not very expensive and to be honest no time to evaluate other software at this point.

Incentivized

The UI is more complex than I would like. Part of the challenge is that most users use PagerDuty infrequently; I don't remember how I changed a policy last time. Another part of the challenge is that some users expect alerting to be a trivial feature, and are reluctant to invest any time in reading the documentation.

Incentivized

PagerDuty is reliable and easy to set up. It gives an effective way to notify the team about critical incidents which results in a faster turnaround time on issues. users can customize their alerts rules based on their preferences. Overall it's effective and easy to use which adds great business value.

Incentivized

When I setup notifications to PD thru the Python API I was impressed with the ease with which I could set up the software/service.

Incentivized

OpsGenie was useful, mainly for teams already using Atlassian tools, and xMatters was good for handling team communication during incidents, but PagerDuty felt more complete for managing the full incident process in one place. We went with PagerDuty because it manages alerts, escalations, and on-call duties in a more organized and dependable way, which fits better with how our teams work daily.

• If patients can talk to an on-call provider, it may save them from having to go to the ER.
• Patients can get prescriptions after hours. The medication we prescribed saves lives.
• Patients are more likely to stay enrolled in our program if they access care after hours.

Incentivized