Re:Monitors.txt - lazy webapp monitoring
by ricardobeat on Saturday November 05, 2011 @04:01PM
(#3200750)
I'd much rather have something akin to an appcache.manifest file:
IMO feature testing should be part of your test suite pre-deploy, not the monitoring service.
[ Parent
| on HN ]
Re:Monitors.txt - lazy webapp monitoring
by eliot_sykes on Saturday November 05, 2011 @04:04PM
(#3200759)
Thanks for the suggestion, I like how succinct it is.
monitors.txt's purpose isn't to replace testing new features during development. Monitors.txt replaces the process of logging on to a 3rd party's app to configure the monitoring for the new feature.
Re:Monitors.txt - lazy webapp monitoring
by merlincorey on Saturday November 05, 2011 @08:41PM
(#3201400)
This syntax seems a lot less confusing and more powerful than the subset of English presented.
Another bit of syntax that I think is missing is something like:
GUAGE:
http://domain/stats/logins 60s
COUNTER: http://domain/stats/logins 60s
AVG: http://domain/stats/logins 24h
Something like this would allow you to setup not only with simple external monitoring systems, but with internal systems like Nagios, Ganglia, ZenOSS, etc.Of course, I do have to agree with many people that I am a bit uneasy PUBLISHING all of this data for all to see.
Re:Monitors.txt - lazy webapp monitoring
by eliot_sykes on Saturday November 05, 2011 @10:19PM
(#3201585)
Interesting, incorporated this into the YAML sample: https://github.com/eliotsykes/monitorstxt/blob/gh-pages/moni...