I used the migration tool to migrate my v1 rules to v2, trying to migrate. I’m on the latest 2.4.0b4. What I’m noticing is that, by default, the certificate doesn’t seem to be monitored after migration:
Here is the rule configuration:
What exactly is missing? Why is the certificate not monitored like with the v1 plugin?
What exactly is missing? Why is the certificate not monitored like with the v1 plugin
Nothing is missing, its just that in the Check http webservice it is not included in the details.
It does however correctly alert when the certificate thresholds are reched.
If you are only interested in the certificate then do not use the Check HTTP webservice, but the Check certificate rule.
example:
i also was struggling with the new Check http webservice for just checking the certificate.
Then someone on the forum pointed out ( same as i am doing now) the Check Certificate rule.
made my life alot easier.
Thank you, didn’t even know that existed. I do monitor both the website and the certificate, with v1 it had to be 2 separate checks so this is why I had it set up this way. So I will say this: the parameters of the v2 plugin are a little bit confusing here, as it makes it seem like we should be able to monitor the certificate within the same check.
You can monitor the certificate with the same check, however the ‘summary’ regarding certificate expiry is not included in output …
It does alert correctly when certificate reaches defined thresholds
Inside the details output you also see the validity before any warning is given.
you are right, i wanted to write ‘summary’ … but mistakenly wrote detail … corrected it 
So I’ve been able to figure out pretty much everything now, but noticed the “Clickable URL” option is not there anymore? Curious what’s the reasoning behind this?
Other than that, the only thing I don’t like is the very generic error sending request for url we sometimes get, such as when I’m trying to follow redirections (it doesn’t work, unsure why, a more verbose error would be of great help).
Edit: my problem seems to be with local self-signed certificates and HTTPS for web pages such as UPS, PDU and many other network equipments. Kind of a pain really, if there is a way to just ignore the insecure certificate for the purpose of checking that the webpage is up and has a string like before, that would be great.
