Item: PagerDuty
Rating: 6
Author: Verified User

Use Cases and Deployment Scope

We use pagerduty in our clients information system to recover, analyse and create alerts based on the cloud provider logging service.
PagerDuty is then configured to send alerts to specific users

Pros and Cons

Interface with certain cloud providers
Alerting configuration
Log & alerts visualisation

Clear documentation on the implementation using IaC tools
Poor community around the solution

PagerDuty Reliability

Until now we haven't encountered maintenance or downtime issue (we are using the SaaS solution either for pagerduty or the pagerduty integration service on the cloud provider)

PagerDuty Integrations

One benefit is that we were able to migrate between cloud providers without issues and by keeping both services up and running in the meanwhile. The transition has been smooth so far.

It is hard to compare these solutions.
PagerDuty is currently being used in SaaS version, whereas Grafana & Loki are mainly implemented next to the packaged app.
The second solution, although time consuming and requiring maintenance is still a viable option. However, PagerDuty is better suited for multi-cloud and ease of use.

Key Insights

Do you think PagerDuty delivers good value for the price?

Yes

Are you happy with PagerDuty's feature set?

Yes

Did PagerDuty live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of PagerDuty go as expected?

Would you buy PagerDuty again?

Yes

Other Software Used

Grafana Loki, Prometheus

Likelihood to Recommend

Using pagerduty provides a SaaS solution ready to use, however, other (open source) solutions seem to be better suited such as the Elastic seach, Logstash and Kibana stack or Loki and Grafana. The main issue around pagerduty is the documentation. Once the documentation figured out, the implementation is pretty eazy.

PagerDuty SaaS and its integration with cloud providers

Overall Satisfaction with PagerDuty