On Tue, Oct 20, 2020, at 08:52, Nemanja Delic wrote:
> In this case the cert has expired on Oct 13 22:12:47 2020 GMT. Since it's not
> last one in chain it's not breaking things. I can set the filter accordingly
> ( with smth like > -7), just thought there might be some other solution.
PKIX pat
Brian,
Using pretty much standard Blackbox job config:
- job_name: blackbox
honor_timestamps: true
params:
module:
- http_2xx
scrape_interval: 1m
scrape_timeout: 1m
metrics_path: /probe
scheme: http
file_sd_configs:
- files:
- /etc/prometheus/file_sd_config.d/blackbox_
Any certificate in the chain which is expired or invalid will "break
things": i.e. clients will not accept the certificate as valid, if they
cannot establish a chain of trust back to the root.
>From the linked github discussion about negative time to expire, I
understood these would be hugely n
Hi Brian,
In this case the cert has expired on Oct 13 22:12:47 2020 GMT. Since it's
not last one in chain it's not breaking things. I can set the filter
accordingly ( with smth like > -7), just thought there might be some other
solution.
On Tue, Oct 20, 2020 at 12:20 PM Brian Candler wrote:
>
Filter it to ignore values which are "too negative":
expr: (probe_ssl_earliest_cert_expiry - time()) / 86400 < 14 > -365
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send
5 matches
Mail list logo
