PD: Still the industry leader, but with some flaws that if not addressed will allow others in the space to catch up.

PagerDuty is used across the operations, support, and dev organizations but is primarily used by operations. We use PagerDuty in operations for all alerting from our monitoring systems as well as coordinating service incident response. Dev/Support use PD for responding to service incidents.

In terms of triggering alerts and sending initial notifications, PD lives up to its mission. As stated, the pain for us is on service incidents notifying multiple parties reliably without acks from one party affecting others.

The amount of integrations with PD is helpful and impressive. I've been able to find integrations for just about every monitoring tool I've used. The only challenge has been with Splunk, where the integration cannot close incidents on an automated basis. I worked around this by using the email integration, regexes for opening and closing an incident based on a key in the email subject, and wrote a Splunk query that's the inverse of my trigger query to get the automated outcome needed. This approach does turn the alert into a trailing indicator, but its better than nothing.

We do not use the modern incident response package. Upon the last look at it, it was cost-prohibitive for us.

The only value we've received out of analytics to date is understanding alert volume per team and responder.