DERDACK Enterprise Alert vs. PagerDuty

DERDACK Enterprise Alert is extremely well suited, when different teams (subject matter experts) are involved in the technical support process. Quick and easy responses (acknowledgements, exection of scripts/tasks/processes, etc.) are key. Also, DERDACK Enterprise Alert is on one hand easy to deploy, but API offers a variety of customized integrations.

Incentivized

I've used ICM in the past which has been a very Microsoft product with everything thrown into a blender. So, PD implementation is a breath of fresh air with focused pages to achieve the end goal. If the goal is to collaborate on issues across the organization, PD might not be the best solution but within specific teams, PD excels at it.

Incentivized

• Self Managed On-Call scheduling for teams.
• Ability to back track an alert and review the stages of escalation.

Incentivized

• Alerting notifications is its best attribute; it will continue to make contact until the alert is acknowledged by a user.
• The calendar view provides valuable information regarding who is on call by the team and their full contact information.
• The application also lets you initiate a tech bridge meeting instantly and notifies all on-call users.

Incentivized

• More integrations with other ITSM vendors

Incentivized

• When getting a phone call, PagerDuty doesn't seem to allow acknowledgments of alerts through the phone, which it says it does. I constantly receive a message that it was updated by another person - when in reality, it wasn't.
• Smarter notifications. If an alert was snoozed for a time, when it comes back, it sends out another alert. It should, I think, send a message asking if the alert is still an issue and give the option to close.
• Make schedule changes more intuitive.
• One button to acknowledge and close an alert.

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

Very intuitive use, almost no training necessary.

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

The best experience.

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

Cost of ownership was more than double in more than five years.

Incentivized

I have not use the 2 technologies for as long as I have used PagerDuty but in my opinion PagerDuty makes things a lot easier. The other tools got the job done and got alerts out but PagerDuty just seemed to make the setup for on-call alert schedules and integrations easier than the others. This isn't to say the others are difficult, just that PagerDuty was slightly better. I also have noticed that more tools have options to integrate to PagerDuty over the other tools.

Incentivized

• It supports us not to incur penalties of missed SLAs - clients and internal

Incentivized

• Allow our service to be available 24/7 with minimal downtime, improving customer experience
• Monitor incidents and allow us to customize/schedule alert notifications, making engineers' jobs easier and preventing turnover
• Prevent SEVs that could deteriorate, bring down our service, and cost us millions of dollars from loss in bookings

Incentivized