PagerDuty

The platform is highly configurable. Features like bidirectional status sync, urgency per audience, and the ability to separate executive-level notifications from engineering alerts have significantly reduced noise and prevented inappropriate escalations to our engineering on-call. Integration with our monitoring tools works smoothly, ensuring issues such as event-queue spikes or login failure patterns reach the right teams quickly. The strong incident visibility and the ability to adjust priority levels dynamically has helped us streamline our workflows.

Compliance, security, and help from the vendor on highly available large-scale cloud and on-premise deployments. This ensures peace of mind during incidents and compliance audits.

That it has a long list of integrations with different observability and alerting tools, basically you can intergrate pagerduty with virtually any vendor

Tuning alerts can be time consuming, especially when dealing with early morning false positives or traffic based spikes. Until the thresholds, time of day and sampling windows are fully tuned, we occasionally saw false positives or early morning spikes. The flexibility of the platform also means that configuration can become complex if not well governed.

PagerDuty operates in a competitive space. They have been innovating over the years with cloud SaaS offerings and more recently with AIOps features. However, the product could benefit from additional innovation, especially related to AI and visualizations, as technological advancements and other vendors move quickly.

Their options for user administration governance is very limited or rigid, when we have to the audit API to able to provide reports on users onboarded and offboarded and tokens generated by those users and when, which is toil for us