Completely agree! I often have to fight that "I could just build that myself" mentality, which glosses over the points you made so well.
It's the same as "Twitter clone" with just posting messages with 140 char limit and "build a blog in 15 minutes".
Alerting over a downed website are is sorta like a glacier, there's so much under the surface, if you just see the surface you're missing out.
1. Multiple locations 2. Multiple check intervals 3. SMS/email provider switch on fail 4. Auto recovery of your checkers 5. Multiple providers with a single storage.
You make valid points about redundancy and levels of reliability but keep in mind that even Pingdom can go down: http://royal.pingdom.com/2016/10/24/ddos-attack-affects-ping...
Diversify to avoid cascading failures ;)
Multiple ping locations is helpful in bringing more data points, but it doesn't address the problem of explaining what the data means. For example, pingdom could provide triangulation of the failure if fault identification was part of the businesses model of monitoring.
I would describe the criticism of pingdom as a failure of expectations. Pingdom is not a security service, a monitoring service, or fault identification service. They are a single test, and the data you get back is useless unless interpreted and verified.
If you're providing a service to your users, and they say that the service is down using pingdom, you should be looking into, not just saying "Works on my machine".
I mean, what qualifies as “being up”? If some random link in the middle of the Internet goes down, and you suddenly, for 30 seconds, are unreachable for the few hundred people going through that exact link because it happens to be the best path between those people and your server, can they claim that you have failed to provide adequate uptime? If such a fault happens, are you then responsible to troubleshoot it? I say no. The Internet is the ISP’s responsibility, and the only faults actually meaningful to report to your ISP are the repeatable or long-lasting ones. Small stuff like this is not worth anybody’s time (except ISPs) to go digging into.
You've seem to think that you have to investigate the issues. On the contrary, you bump it up to your isp to investigate. If your ISP is regularly having these issues then it might be time to change ISPs to one with a better peering agreement.
1. Reported as being experienced by an actual user of a web site,
2. Longer than a a couple of minutes at most (usually just a few seconds),
3. or happened more frequently than a few times per month,
then I might consider reporting it to my ISP. As it is, it’s not worth it. “Cosmic rays, man.” (https://www.joelonsoftware.com/2001/07/31/hard-assed-bug-fix...).
If Pingdom can't get to your site, it's highly likely your users can't either.
Also, if you want a 'proper' ops alerting SaaS, you're looking at something along the lines of $50/user/mo or $15/server/mo, neither of which is trivial.
Too many things can go wrong and you are all around better off outsourcing this to something like Pingdom. You don't have sufficient levels of reliability, you aren't dual homed across twilio and another phone system. Maybe the cause of your outage is that AWS is having issues. Now your site and your monitoring is down.
Much better to outsource to people who obsess over doing this right and making sure they are properly redundant.