From d1bbe73a0871eedab0d98140d0a7a31d25402b3e Mon Sep 17 00:00:00 2001 From: Rob Best Date: Wed, 20 Mar 2019 18:07:18 +0000 Subject: [PATCH] Update README and examples for tls changes --- README.md | 10 +++++----- examples/example.prometheus.yml | 10 +++++----- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index dd6d6cc..39cfee2 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Whatever it is, the SSL exporter gives you visibility over those dimensions at t make ./ssl_exporter -Similarly to the blackbox_exporter, visiting [http://localhost:9219/probe?target=https://example.com](http://localhost:9219/probe?target=https://example.com) will return certificate metrics for example.com. The ```ssl_https_connect_success``` metric indicates if the probe has been successful. +Similarly to the blackbox_exporter, visiting [http://localhost:9219/probe?target=example.com:443](http://localhost:9219/probe?target=example.com:443) will return certificate metrics for example.com. The ```ssl_tls_connect_success``` metric indicates if the probe has been successful. ## Docker docker pull ribbybibby/ssl-exporter @@ -41,7 +41,7 @@ I considered having a series for each ```ssl_cert_subject_alternative_*``` value | ssl_cert_subject_alternative_emails | The subject alternative email addresses (if any). Always has a value of 1 | issuer_cn, serial_no, emails | | ssl_cert_subject_alternative_ips | The subject alternative IP addresses (if any). Always has a value of 1 | issuer_cn, serial_no, ips | | ssl_cert_subject_organization_units | The subject organization names (if any). Always has a value of 1. | issuer_cn, serial_no, subject_ou | -| ssl_https_connect_success | Was the HTTPS connection successful? Boolean. | | +| ssl_tls_connect_success | Was the TLS connection successful? Boolean. | | ## Prometheus ### Configuration @@ -52,8 +52,8 @@ scrape_configs: metrics_path: /probe static_configs: - targets: - - https://example.com - - https://prometheus.io + - example.com:443 + - prometheus.io:443 relabel_configs: - source_labels: [__address__] target_label: __param_target @@ -79,7 +79,7 @@ Number of certificates in the chain: Identify instances that have failed to create a valid SSL connection: - ssl_https_connect_success == 0 + ssl_tls_connect_success == 0 ## Client authentication The exporter optionally supports client authentication, which can be toggled on by providing the `--tls.client-auth` flag. By default, it will use the host system's root CA bundle and attempt to use `./cert.pem` and `./key.pem` as the client certificate and key, respectively. You can override these defaults with `--tls.cacert`, `--tls.cert` and `--tls.key`. diff --git a/examples/example.prometheus.yml b/examples/example.prometheus.yml index 1e1871d..82addb6 100644 --- a/examples/example.prometheus.yml +++ b/examples/example.prometheus.yml @@ -6,11 +6,11 @@ scrape_configs: metrics_path: /probe static_configs: - targets: - - 'https://google.co.uk' - - 'https://prometheus.io' - - 'https://example.com' - - 'https://helloworld.letsencrypt.org' - - 'https://expired.badssl.com' + - 'google.co.uk:443' + - 'prometheus.io:443' + - 'example.com:443' + - 'helloworld.letsencrypt.org:443' + - 'expired.badssl.com:443' relabel_configs: - source_labels: [__address__] target_label: __param_target