It so happens that we are also hiring a ton! Check us out at http://www.pagerduty.com/company/work-with-us/ or reach out to me directly if you're interested in working on hard problems with highly available distributed systems (email in profile).
Congratulations! PagerDuty has an amazing technical team and their focus on reliability is an inspiration (just see their post on Failure Fridays[1]). Which is super important for when your systems are at the worst and require immediate manual help.
This is great. We use the most primitive part of their functionality which is simply alert the right person through the best channel - whenever a part of our system detects that something is wrong. That's all - but I still love it. Hope they continue improving this - it's not perfect yet.
We will continue to keep improving our core functionality, for sure (there are one or two things coming out very soon). With the raise we're hoping to have to make fewer tradeoffs between building X and building Y.
PagerDuty is awesome and so is their android App. We've hooked our entire probing(system test) and code instrumentation through riemann to pagerduty. Each time a developer starts a new branch she can deploy it on the cloud, get into pagerduty console and within a few minutes check if there are any regression failures. Furthermore, production alerts make a "snake attack ssss" notification on my android (which by now everyone recongizes) and if they are not auto-resolved within 10 minutes I get a phone call, and if I don't acknowledge it, another engineer gets a phone call...
It took some time to tweak riemann to avoid the pagerduty throttler but now it works great, and makes our product even greater.
I would only wish pagerduty added a regex filter in the incidents view. It would help us alot.
You can pull in an iCal link from the web UI, if you weren't aware. That way, it will nicely with the rest of your calendars in the apps you already use on a regular basis.
We tried switching to VictorOps and in the first hour their website started crashing our browser.
It turned out each event was rendering in its own frame, and when we had more than a couple hundred alerts, the browser took more memory than available.
Supposedly its fixed now, but I'm not interested in being a beta tester for an alert system.
I've been using OpsGenie, which also offers incoming support phone numbers, and push notifications since day one. They did improve their Android app, but it seems that VictorOps one-ups both PD and OG.
[+] [-] romanhn|11 years ago|reply
[+] [-] DanielRibeiro|11 years ago|reply
[1] http://blog.pagerduty.com/2013/11/failure-friday-at-pagerdut...
[+] [-] empthought|11 years ago|reply
Nope!
[+] [-] nullspace|11 years ago|reply
[+] [-] ultrasaurus|11 years ago|reply
[+] [-] gwintrob|11 years ago|reply
[+] [-] johns|11 years ago|reply
[+] [-] ramoq|11 years ago|reply
[+] [-] itaifrenkel|11 years ago|reply
I would only wish pagerduty added a regex filter in the incidents view. It would help us alot.
[+] [-] aaronblohowiak|11 years ago|reply
[+] [-] kingnothing|11 years ago|reply
[+] [-] ultrasaurus|11 years ago|reply
[+] [-] itsmeduncan|11 years ago|reply
But why does the link go to the comments...?
[+] [-] lanstein|11 years ago|reply
[+] [-] bitonomics|11 years ago|reply
[+] [-] corford|11 years ago|reply
[+] [-] jakozaur|11 years ago|reply
[+] [-] mrtron|11 years ago|reply
[+] [-] ak2196|11 years ago|reply
[+] [-] acchow|11 years ago|reply
[+] [-] ntonozzi|11 years ago|reply
It turned out each event was rendering in its own frame, and when we had more than a couple hundred alerts, the browser took more memory than available.
Supposedly its fixed now, but I'm not interested in being a beta tester for an alert system.
[+] [-] kolev|11 years ago|reply
[+] [-] dredmorbius|11 years ago|reply
Your comment as it stands isn't particularly useful. Specifics would improve it greatly.
[+] [-] kanwisher|11 years ago|reply