Wow.
To paraphrase Babbage, I cannot apprehend the confusion of ideas which could lead someone to think this is a good idea.
To paraphrase Babbage, I cannot apprehend the confusion of ideas which could lead someone to think this is a good idea.
1. Reliance on Google Docs' uptime. While any monitoring service will in theory present the same problem, you're putting all your eggs in one basket.
2. It's just the wrong tool for the job. Install and learn Nagios or Zabbix or what-have-you. If you're worried about uptime, get a couple VPSes from different providers and run your monitors from both.
There's nothing utterly horrifying about it technically, but I just can't imagine how one comes up with this answer to the question of monitoring services.
For what it's worth, Google Docs isn't our only monitoring system. We use Munin as our primary monitoring tool, but this is a nice addition to that.
It's also complicated by Google's infrastructure — services are scattered across many, many servers, and Google's outages tend to be on some subset of services and/or servers. Your Nagios checks are probably not always checking the same endpoint as users connecting.
And its very unreliable. So it spams me despite all my efforts to remove it.
I finally made a new filter and archive all notifications.
By the way, Microsoft Office has, at various times, contained a flight simulator, a pinball game, and a first-person shooter.
http://en.wikipedia.org/wiki/Easter_eggs_in_Microsoft_produc...