Feedback of PagerDuty as an Alerting/Monitoring Software from the perspective of a fresher-engineer
February 06, 2024
Feedback of PagerDuty as an Alerting/Monitoring Software from the perspective of a fresher-engineer
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with PagerDuty
PagerDuty is a key monitoring and alerting component that we use org wide for Engineering Teams. The specific business problems that we address by using PagerDuty are
1. Org Wide alerting for critical components like error handling, out-of-memory detections etc
2. Infra based alerts to identify areas where load is a lot, for example if there are excessive arguments on an sidekiq queue
3. Low priority alerting of components as well
1. Org Wide alerting for critical components like error handling, out-of-memory detections etc
2. Infra based alerts to identify areas where load is a lot, for example if there are excessive arguments on an sidekiq queue
3. Low priority alerting of components as well
- Alerting when Infra load becomes a lot eg, Sidekiq Arguments exceeding, Chewy Imports error
- Manually Setup triggers for excessively running jobs
- Error Based Handling based on team for appropriate routing and paging
- Setup of teams, schedules, escalation policies with clear paths of instructions
- More capabilities in the Mobile App
- Search capabilities on incidents based on team and user-defined properties
- alerting
- Usefulness of paging-key
- Mobile App
I feel this will be a crucial component because most of our systems rely on using PagerDuty as an alerting component and we do expect no gaps here. However, we do fall back to failsafe mechanisms of debugging / monitoring with reduced capabilities.
I think this external integration is helpful. I have been using the Slack-PagerDuty integration extensively where the alerts are routed by paging-key ==> relevant slack channels. This helps the relevant members of the slack to actually quickly respond to alerts. Apart from that, I am familiar with Jira Integrations which also aid in issue tracking in setups where agile is followed
1. Alerting based on team
2. Escalation Policy
-> Who to message, email, call, notify when the Incident is triggered --> Who to message, email, call, notify, after say 30 mins when the Incident is triggered.
3. Must be acknowledged or else the the SLAs would break.
2. Escalation Policy
-> Who to message, email, call, notify when the Incident is triggered --> Who to message, email, call, notify, after say 30 mins when the Incident is triggered.
3. Must be acknowledged or else the the SLAs would break.
PagerDuty has its advantages and costs associated. We use alternative to mitigate risk of failure, priority and effectiveness.
Do you think PagerDuty delivers good value for the price?
Not sure
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?
I wasn't involved with the implementation phase
Would you buy PagerDuty again?
Yes