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
Monitoring https ingresses with blackbox gives some useful insights like ssl expiry you don't have if
you just monitor the associated service with http. Also in case your service only serve https with a public certificate, monitoring the associated service gives you a certificate error because the target of blackbox is service.namespace.svc which doesn't match the name associated with the certificate.
The standard Prometheus Ingress scrape config (for those with a Blackbox exporter) is ok. But I don't want to expand to providing Blackbox Exporter manifests or graphs (also I don't copy-paste others' graphs) or tracking those releases. Users can manage that.
Description
Monitoring https ingresses with blackbox gives some useful insights like ssl expiry you don't have if
you just monitor the associated service with http. Also in case your service only serve https with a public certificate, monitoring the associated service gives you a certificate error because the target of blackbox is service.namespace.svc which doesn't match the name associated with the certificate.
Steps to Reproduce
Expected behavior
Environment
Possible Solution
add a new job to prometheus config
add change prometheus clusterrole to allow listing of ingress
Now you just have to add the annotation
prometheus.io/probe: "true"
to you ingressesThe text was updated successfully, but these errors were encountered: