/.well-known/ http://tools.ietf.org/html/draft-hammer-hostmeta-17
Re:Monitors.txt - lazy webapp monitoring
by eliot_sykes on Saturday November 05, 2011 @02:44PM
(#3200558)
I'm keen on your idea for an out-of-band mechanism, and would be needed for the obfuscated URL idea
"For the more gung-ho, obfuscate the URL and use SSL (e.g. https://yoursite.tld/something-unguessable/monitors.txt) and tell your provider where to find your monitors.txt"
• shoehorn a pointer to a varying URL inside an existing convention-dictated place – as for example with sitemap pointers inside robots.txt files.
• let the resource live anywhere but specify its location to consuming services via some out-of-band mechanism. That is, you still have to tell any monitoring provider where your particular monitoring-spec lives, probably via its signup interface, but you can still use the same format and unmoving file with multiple providers.