Am March 19, 2020 2:07:03 PM UTC schrieb Michael Matz
The two important "services" on that would be a simple HTTPS check on some random URL, let's say https://gcc.opensuse.org/ (better would be https://gcc.opensuse.org/gcc-old/SPEC/CINT/sb-czerny-head-64-2006/recent.htm...
Ok: done.
and a check that would verify rsync via ssh access (that is what got broken, the webserver continued to work), from inside the SUSE network. I don't know if you have the capability to do such checking. (I could add a ssh key for that purpose).
I think I don't need to be inside the SUSE network to test of a rsync via ssh to this machine works: shouldn't it be enough to test this from the monitoring server? I would suggest to create a local user for this - and test transfers as this user. This should not be too intrusive (the user can be very limited) but in the other side allow to see if the service works in general. I have to admit that this of course does not cover network issues to the SUSE side - but these might be another check. You could also consider to sync a file containing a timestamp in your script. Let's say: https://gcc.opensuse.org/.last_sync - containing something like "2020-03-19 22:02:03". Our monitoring could download the file, parse it's content, and alert if the date is older than a day (or whenever your sync normally runs). What do you think? [ ] test ssh (sync) with local, separate user [ ] test freshness of delivered content via special file Regards, Lars -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org