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
Since #463 we have the namespace label on metrics. 🎉
This is great but it clashes with the default namespace label , eg: namespace="sealed-secrets" that Prometheus adds as part of service discovery.
This means that any dashboards and alerts will still have sealed-secrets as the namespace instead the namespace the secret was unable to be unsealed in, eg: test.
We can prefer the controller's metric namespace, eg: test by toggling the honor_labels flag to true in the PodMonitor per docs snippet:
# honor_labels controls how Prometheus handles conflicts between labels that are
# already present in scraped data and labels that Prometheus would attach
# server-side ("job" and "instance" labels, manually configured target
# labels, and labels generated by service discovery implementations).
#
# If honor_labels is set to "true", label conflicts are resolved by keeping label
# values from the scraped data and ignoring the conflicting server-side labels.
#
# If honor_labels is set to "false", label conflicts are resolved by renaming
# conflicting labels in the scraped data to "exported_<original-label>" (for
# example "exported_instance", "exported_job") and then attaching server-side
# labels.
<snip>
[ honor_labels: <boolean> | default = false ]
The text was updated successfully, but these errors were encountered:
Since #463 we have the
namespace
label on metrics. 🎉This is great but it clashes with the default namespace label , eg:
namespace="sealed-secrets"
that Prometheus adds as part of service discovery.This means that any dashboards and alerts will still have
sealed-secrets
as the namespace instead the namespace the secret was unable to be unsealed in, eg:test
.We can prefer the controller's metric namespace, eg:
test
by toggling thehonor_labels
flag to true in thePodMonitor
per docs snippet:The text was updated successfully, but these errors were encountered: