4 ms·
I like the idea. What about if the definition was in the form of HTTP requests, something like: GET / GET /login POST /login user={{CUSTID}}&
by delano 15y ago
I like the idea. What about if the definition was in the form of HTTP requests, something like:
GET /
GET /login
POST /login
user={{CUSTID}}&pass={{PWORD}}
GET /search?q={{QUERY}}
The monitors.txt file could contain pointers to the definition files (one file per usecase), ideally with arbitrary metadata.
If there's some kind of consensus, now or later on, I'll implement it in our monitoring service (blamestella.com).
- eliot_sykes 15y agoThanks for the psuedo code and the consideration of implementing it if there's consensus, much appreciated. I'm working on implementing monitors.txt for my own sites and will open it up to a few devs to get the API sculpted just right. After then I hope they'll be other monitoring services as keen as blamestella to have a go at it.