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
Like with enforcedSampleLimit and sampleLimit, we want to enforce minimal values at the Prometheus CRD level as well as support individual limits per ServiceMonitor, PodMonitor and Probe resources.
The text was updated successfully, but these errors were encountered:
What is missing?
Prometheus v2.27.0 introduced 3 new configuration fields to prevent Prometheus from ingesting metrics with "excessive" labels:
label_limit
label_name_length_limit
label_value_length_limit
The Prometheus operator should expose these fields in its CRDs.
See prometheus/prometheus#8291 for details.
Why do we need it?
Feature parity with Prometheus :)
Environment
N/A
Anything else we need to know?:
Like with
enforcedSampleLimit
andsampleLimit
, we want to enforce minimal values at the Prometheus CRD level as well as support individual limits per ServiceMonitor, PodMonitor and Probe resources.The text was updated successfully, but these errors were encountered: