Live data from Hacker News

PagerDuty (YC S10) wakes the right person up for your tech emergencies

readwriteweb.com

21–25 of 25 posts

Re: PagerDuty (YC S10) wakes the right person up for your tech emergencies

#22

And this is better than widely adopted, open source Nagios how?

It is nothing like Nagios. PagerDuty handles alerting, not monitoring. Once your monitoring system discovers something is wrong, it tells PagerDuty. PagerDuty then gets ahold of the right person. It lets you set up on-call rotations. It does automatic escalation if the primary contact doesn't acknowledge the incident. If your monitoring system supports it, it will even automatically resolve the incident once you fix your servers.

Re: PagerDuty (YC S10) wakes the right person up for your tech emergencies

#23

Earlier quoted context omitted.

We have a simple integration API and we can also integrate with any system that can send email. Regarding the integration, just shoot us an email: support@pagerduty.com.

ok great will do. I was on iphone when i wrote question, yet now looking via old fashion computer Im not easily seeing it on your site.

Was looking for it too, found it: http://www.pagerduty.com/docs/api/api-documentation took a while, though -- in my opinion, a link to the API documentation is important enough to put in the footer, maybe next to or under "integration guides".

Re: PagerDuty (YC S10) wakes the right person up for your tech emergencies

#25

And this is better than widely adopted, open source Nagios how?

It is nothing like Nagios. PagerDuty handles alerting, not monitoring. Once your monitoring system discovers something is wrong, it tells PagerDuty. PagerDuty then gets ahold of the right person. It lets you set up on-call rotations. It does automatic escalation if the primary contact doesn't acknowledge the incident. If your monitoring system supports it, it will even automatically resolve the incident once you fix…

In point of fact, Nagios (which I use extensively) handles alerting, notification, auto escalations, acknowledgements, on-call rotations, and resets itself post incident. http://library.nagios.com/ Sounds like re-inventing the wheel for a well-solved problem.
Post reply on HN