Updated tls_expiry description to better reflect when host is different to the sni name#1922
Merged
jamesoff merged 1 commit intoMay 30, 2026
Conversation
steven-geo
changed the title
Owner
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This changes the message 'Detail' from the tls_expiry monitor. The update only impacts the detail when sni is specified and the sni is different to the hostname used. This is useful when specifying an IP address name for a host, but still checking for a valid SNI named certificate.
Example Monitor
[mytlsexpirymonitor]
type=tls_expiry
host=1.2.3.4
port=443
min_days=21
sni=mycertificate.com
Original message:
Certificate at 1.2.3.4:443 has 53 days left to expiry
New Message:
Certificate mycertificate.com at 1.2.3.4:443 has 53 days left to expiry