PagerDuty review after 2 years of usage
Overall Satisfaction with PagerDuty
In my current and previous production system Datadog and Sumologic are tools used for observability and they are configured to send alerts to PagerDuty for errors or warning as per user/customer specific thresholds. We are using webhooks to implement this integration. We have customer specific rule sets and thresholds.
Pros
- Automatic Alerting
- Automatic incident management
- Smart false alert detection
- easy and multiproduct integration
Cons
- There are limited number of APIs can be configured which can improve as per customer demand
- Some manual configuration work can be avoided with use of infrastructure as a code
- Cost of product increases with load on system
- Automation in alerting
- Error / Exception workflow management
- Production support
- Production incident resolution time decreased by 30%
- Incident management process has reduced overhead of support analyst
- More efficient use of support analyst time means faster root cause analysis
During DR testing support analyst trust on PagerDuty to generate alert and ensure user experience is not impacted due to such change of production environment. Our organization is using PagerDuty for long time now and smart alerting mechanism has reduced false alert by at least 25%
Inbound integration with Datadog or Sumologic
Outbound integration SMS or call
Outbound integration SMS or call
Not applicable
Current implementation has integration with Slack channel which has helped alot during office shift changes. All the involved parties are aware of incident and progress.
Not aware of other products
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?
Yes
Would you buy PagerDuty again?
Yes
Comments
Please log in to join the conversation