PagerDuty covers our data flow
August 11, 2020
PagerDuty covers our data flow
Team Lead in EngineeringMarketing & Advertising Company, 201-500 employees
Score 7 out of 10
Overall Satisfaction with PagerDuty
PagerDuty is used mostly by our engineering team but also some of our client support teams. The Support team uses it to get quicker feedback if something goes wrong so they can either take action or know when issues arise immediately. Our company manages a data warehouse so we rely on getting data from various sources on an hourly, daily, weekly, and monthly basis. If we receive alerts, our Support team can reach out to our vendors to find out what the issue is. They can also inform our clients if there are any delays.
Our Engineering team uses it to monitor our 200+ processes. We would be able to keep track if we had to backfill any data but we now use an open-source data flow management tool to automatically trigger data backfills. PagerDuty is still useful for being aware of the ongoing issues whether it is on our side or the vendor/client-side.
- We get real-time notifications from our applications so we can immediately take action.
- The escalation policies are useful for setting certain engineers responsible right away or having a backup available.
- The UI is very simple and easy to use. Easy for non-technical employees to manage alerts.
- I wish use groups were not a premium feature. This is such a basic feature to me.
- Better grouping of alerts from the same services. In the UI, sometimes a process can trigger many alerts and it would be helpful if the UI could organize them.
PagerDuty has been relatively stable but we do periodically receive alerts from PagerDuty themselves. The issues are often short and intermittent, which has not really prevented us from receiving our own alerts. For context, we are a relatively small Engineering team and we do not host any critical client-facing apps, we rely on PagerDuty for our data warehouse.
We do really make use of any of the integrations except for Slack. We ended up writing our own bot that periodically scans the active alerts in PagerDuty and sends a DM notification in Slack to any users in the alerts. This allows us to minimize the "noise" in our channels. Our wrapper handles what would be 99% of our alerts.
We wrap our data pipeline processes so that when an error occurs, it will trigger a PagerDuty alert and allows to keep an oversight of all of our data. Prior to using an open-source data flow management tool, we would rely on PagerDuty so that we could backfill any data when possible. Our open-source data flow management tool now handles that backfills for us automatically so we mostly use PagerDuty for oversight.
Do you think PagerDuty delivers good value for the price?
Are you happy with PagerDuty's feature set?
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?
Our team wrote our own Python wrapper using PagerDuty's opensource library. The wrapper captures the entire python error message and we post that to our alerts. This allows us to react faster and figure out what the issue is. The UI is simple and easy enough for non-technical folks to use.