What is the advantage of pulling Ruby in versus adding the -f follow option to the existing check_http check?

https://www.monitoring-plugins.org/doc/man/check_http.html

The `-f` flag only states checks that there is a redirect, not what url is redirected to.

The motivation here is that the redirect url already got broken once by accident.

I guess that's a good reason to do this. Please document what the package requirements are for Ruby although since creation of status is not in fact automated it's less of a priority than it would be if the thing were properly put together in the first place.

This would be a good example of the prototype sticking around, I guess.

Adam Thornton The gem turned out to be a bit of a pita on el7 due to the old system ruby but I think I've come up with a reasonable solution by using an SCL. I've opened a PR that adds cut'n'pastable install instructions for sensu-plugins-http, checks for sw.lsstcorp.org, and additional checks for eups.lsst.codes. Needless to say, the nagios configs are untested as there is no automated deployment to test with.