The content on the site may vary a lot, but it should never include words like "exception" or "error", which is what we want to check for.
Thomas Svensen
Created on April 03, 2017 · Last update on July 16, 2024
4 Comments
Eric Mueller
Actually, I have a site that currently has a "Coming soon" page -- I want to know if somehow the site is launched before it should, and the words "Coming soon" disappear. I'd love a "does not contain" option.
Thanks for this suggestion but I decided against implementing this feature. Because I think it's way too easy to generate false positives where your service is down and you're not notified because it's not the case you expected and entered in the search. For example your page could later change "BAD" to "bad" or "DOWN" or whaterver, or your page could simply stop working and returning any text or return an error message instead, and you don't want those to be considered UP. And even if it's not technically my fault, friends don't let friends build brittle monitoring ☺
The better option if you already have a custom status page is to either return a custom HTTP status depending on global state, applying the rules you want (e.g. any service is bad, status = 500) Or you can include a global text status saying something like "Global: UP" and do a positive match on this one.
4 Comments
Actually, I have a site that currently has a "Coming soon" page -- I want to know if somehow the site is launched before it should, and the words "Coming soon" disappear. I'd love a "does not contain" option.
I would like to have this option too. Just to monitor content on the page. People use your service for much more than server monitoring.
This would be handy! Can't you just allow it but add a warning "not recommended" if you don't think its good practice?
Thanks for this suggestion but I decided against implementing this feature. Because I think it's way too easy to generate false positives where your service is down and you're not notified because it's not the case you expected and entered in the search. For example your page could later change "BAD" to "bad" or "DOWN" or whaterver, or your page could simply stop working and returning any text or return an error message instead, and you don't want those to be considered UP. And even if it's not technically my fault, friends don't let friends build brittle monitoring ☺
The better option if you already have a custom status page is to either return a custom HTTP status depending on global state, applying the rules you want (e.g. any service is bad, status = 500) Or you can include a global text status saying something like "Global: UP" and do a positive match on this one.
Sign in to comment