Add riemann-tls-check to monitor TLS certificates
#253
Conversation
This file contains 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
smortex
force-pushed
the
tls
branch
4 times, most recently
from
2fc9da2
to
7898c49
Compare
smortex
changed the title
riemann-tls-check to monitor TLS resourcesriemann-tls-check to monitor TLS certificates
smortex
force-pushed
the
tls
branch
8 times, most recently
from
8d55c7f
to
c9191bb
Compare
Merged
smortex
force-pushed
the
tls
branch
3 times, most recently
from
fa8f899
to
747df08
Compare
smortex
force-pushed
the
tls
branch
2 times, most recently
from
06ed682
to
2225906
Compare
|
I have been using this for some time at $WORK. I think it is ready for production! |
smortex
force-pushed
the
tls
branch
4 times, most recently
from
2ac7246
to
08e8fa9
Compare
Add a riemann-tls-check that accept a list of URI of resources to check TLS certificates. For each URI, resolve the IP addresses that provide the service, and for each IP address generate 6 events for: 1. availability: state (reachability + status of all the following metrics); 2. not after: state + metric (number of seconds until the certificate is expired); 3. not before: state + metric (number of seconds since the certificate is valid); 4. identity: state (certificate subject match the URI hostname); 5. trust: state (validity of the certificate trust chain); 6. OCSP satus: state (validity of the OCSP status if applicable). A STARTTLS handshake is automatically done for imap://, ldap:// and smtp://; a protocol specific handshake is done for mysql:// and postgres:// URI.
|
@jamtur01 may I have a review please? I would like to do a new release soon with all the recent changes 😉. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add a
riemann-tls-checkthat accept a list of URI of resources to check TLS certificates.For each URI, resolve the IP addresses that provide the service, and for each IP address perform a TLS handshake and generate events from the certificate:
(icons legend: 🆗/💥 => the metric report a status (ok, warning, critical); 📉 + 📈 => the metric report a metric)
A STARTTLS handshake is automatically done for
imap://,ldap://andsmtp://URI.A protocol specific handshake is done for
mysql://andpostgres://URI.Limitations
The required API in OpenSSL to check for OCSP Stapling is not currently part of the openssl gem, so this cannot be tested at the moment: ruby/openssl#401