Yes. Every penny ($90/mo). We've been using them at $SMALL_ISP since September 2010. The scheduling, reporting, and flexible alerting has been well worth it to us.
Before PagerDuty we were using Nagios with a modem dialing out to pagers. Later we went to Nagios with email to SMS gateways. We had "problems" with email to SMS delivery and no way to tell if it was a bad employee or flaky cellco gateway. We also had problems with scheduling on call rotation & overrides for vacation.
The escalation/accountability & reporting let us weed out a bad employee that was ignoring pages. We suspected it but phone call delivery with confirmation in Pagerduty ensured there weren't any plausible excuses.
Most importantly it makes scheduling oncall rotations painless.
Yes, you can do all this in plain old Nagios with enough time or hackery. We reached a point where we couldn't waste time on that kind of hackery (changing alert schedules & escalation every time someone went on vacation, google calendar to nagios config scripts) and needed it to just work.
These APIs are just icing on top. I have two projects that will benefit immediately:
1. Our customer service manager has been asking for a easy way to tell who is on call and we didn't want to give her a pager duty login. Now I can make a simple "who is on call?" dashboard so the call center knows who to call if there's a problem monitoring missed.
2. With the Integration Triggers we can open Jira tickets for incidents. This will streamline workflow.
You should checkout the following blog post as a possible solution to item 1 on your list. You can setup a phone number that will page the on-call person.
Comments
Yes. Every penny ($90/mo). We've been using them at $SMALL_ISP since September 2010. The scheduling, reporting, and flexible alerting has been well worth it to us.
Before PagerDuty we were using Nagios with a modem dialing out to pagers. Later we went to Nagios with email to SMS gateways. We had "problems" with email to SMS delivery and no way to tell if it was a bad employee or flaky cellco gateway. We also had problems with scheduling on call rotation & overrides for vacation.
The escalation/accountability & reporting let us weed out a bad employee that was ignoring pages. We suspected it but phone call delivery with confirmation in Pagerduty ensured there weren't any plausible excuses.
Most importantly it makes scheduling oncall rotations painless.
Yes, you can do all this in plain old Nagios with enough time or hackery. We reached a point where we couldn't waste time on that kind of hackery (changing alert schedules & escalation every time someone went on vacation, google calendar to nagios config scripts) and needed it to just work.
These APIs are just icing on top. I have two projects that will benefit immediately: 1. Our customer service manager has been asking for a easy way to tell who is on call and we didn't want to give her a pager duty login. Now I can make a simple "who is on call?" dashboard so the call center knows who to call if there's a problem monitoring missed. 2. With the Integration Triggers we can open Jira tickets for incidents. This will streamline workflow.
You should checkout the following blog post as a possible solution to item 1 on your list. You can setup a phone number that will page the on-call person.
http://blog.pagerduty.com/2012/08/how-to-provide-24x7-phone-...