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
If someone goes looking for that metric in Prometheus / Grafana charts while setting up an OPA deployment, they definitely won't see it! 😅
Expected solution
The docs should reflect the removal of the metric, either with an explicit deprecation/removal note, or by just removing the table row for go_memstats_gc_cpu_fraction.
…s_gc_cpu_fraction`
Prometheus appears to have dropped the `go_memstats_gc_cpu_fraction`
metric, since at least Go 1.18. This commit drops the missing metric
from the table of expected metrics for OPA on the monitoring docs page.
Reference: prometheus/client_golang#1500Fixes: open-policy-agent#6783
Signed-off-by: Philip Conrad <[email protected]>
…s_gc_cpu_fraction`
Prometheus appears to have dropped the `go_memstats_gc_cpu_fraction`
metric, since at least Go 1.18. This commit drops the missing metric
from the table of expected metrics for OPA on the monitoring docs page.
Reference: prometheus/client_golang#1500Fixes: open-policy-agent#6783
Signed-off-by: Philip Conrad <[email protected]>
Short description
Since Go 1.18, it seems that Prometheus has removed the
go_memstats_gc_cpu_fraction
, which is reported on the Monitoring docs page as aSTABLE
metric.If someone goes looking for that metric in Prometheus / Grafana charts while setting up an OPA deployment, they definitely won't see it! 😅
Expected solution
The docs should reflect the removal of the metric, either with an explicit deprecation/removal note, or by just removing the table row for
go_memstats_gc_cpu_fraction
.Additional context
The text was updated successfully, but these errors were encountered: