You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is expected behaviour, but 24 hours after running with --watch-kube-secrets, I could still see metrics for secrets that no longer existed.
Shouldn't the exporter remove them and no longer generate Prometheus metrics for them?
I wanted to add another label to indicate if the cert was a CA or not as my organization mixes them up which seems to work..
But on running a test against the test certs I saw that the bad link pem was getting parsed without error...
$ ./x509-certificate-exporter -d test/
INFO[0000] starting x509-certificate-exporter version 0.0.0 () ()
INFO[0000] 1 valid certificate(s) found in "test/badlink.pem"
INFO[0000] 1 valid certificate(s) found in "test/basic.pem"
Very nice tool and dashboard. Thanks.
I don't know if this is expected behaviour, but 24 hours after running with --watch-kube-secrets, I could still see metrics for secrets that no longer existed.
Shouldn't the exporter remove them and no longer generate Prometheus metrics for them?
I wanted to add another label to indicate if the cert was a CA or not as my organization mixes them up which seems to work..
But on running a test against the test certs I saw that the bad link pem was getting parsed without error...
and generating metrics...
even though it truly does not exist...
The text was updated successfully, but these errors were encountered: