check_http has variables to specify both host address and vhost host
header as well as certificate age. I don't know if you can do
warning/crit for cert age. Also, I'm using a really old check_http, so
your mileage may vary, and I have no idea if the fork in plugins a few
years back impacts this in any way.
This is how I have the check command set up:
>
> # 'check_http' command definition
> define command{
> command_name check_https_vhost_cert
> command_line $USER1$/check_http -I $ARG1$ -H $ARG2$ -p $ARG3$ -C
> $ARG4$
> }
And then service definition:
> define service{
> host_name host.domain.tld
> use http
> service_description HTTPS Cert
> check_command
> check_https_vhost_cert!vhost.domain.tld!webhost.domain.tld!443!90
> }
In this case, host.domain.tld is the base machine, webhost.domain.tld is the
Apache NameVirtualHost , and vhost is a virtual host served out of the
NameVirtualHost address. webhost and host may be the same in your situation.
Tim
On Wed, 2017-02-01 at 20:09 +0000, Charles Breite wrote:
> Trying to configure a check for our SSL certs in Nagios.
>
> Our issue is we have several vhost directories and url’s being served
> from the server.
>
> Can you give me an example of how we can check that the ssl cert is
> valid for say for 14 days and critical at 7.
>
> i.e. server ip is 192.x.x.x and url is https://blah.com
>
> Were probably over thinking this we just want to be able to monitor
> multiple urls on the same server and warn 14 days before expiring.
>
> Thanks
>
> Charles
>
>
>
>
>
>
>
>
>
>
