3 ms·
I wrote a similar tool for monitoring my own servers. Besides being "up", I find that it's important to track slow responses (>10 secs) and to differentiate bet
by xinsight 17y ago
I wrote a similar tool for monitoring my own servers. Besides being "up", I find that it's important to track slow responses (>10 secs) and to differentiate between DNS problems and web server problems.
(I also find that it's useful to check for load, disk space, mysqld is responsive, etc. but that's would take away from the elegance and simplicity of this tool.)
- uggedal 17y agoI close the socket of the connection after 5 seconds. That should identify problems with slow responses. In the notifications that are sent I differentiate between responses that are not 200 OK or matches your criteria, problems with getting to the server (DNS), and problems with parsing the response. Within these three categories I also give additional info (HTTP status code returned etc). Thanks for the feedback,
- cschneid 17y agoOne trick we use for our applications is have an url endpoint that checks for db connection, filesystem, etc and formats it in a human readable and machine checkable format (ie. "Load is OK at .4 .4 .4"). Then you can use a similar "request contains" check to make sure everything is up.