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
Upgraded Kube-State Metrics to 2.8.0, enabled native-histogram feature flag on Prometheus --enable-feature=native-histograms.
What did you expect to see?
Successful scraping of the kube-state-metrics endpoint
What did you see instead? Under which circumstances?
An error of proto: wrong wireType = 0 for field Metric when attempting to scrape the kube-state-metrics pod.
If native-histograms are disabled this error does not appear and it scrapes correctly as expected.
System information
No response
Prometheus version
2.42.0
Prometheus configuration file
No response
Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
I'm unsure whether this is a Kube-state-metrics issue or a Prometheus issue, but as it works when the experimental prometheus feature was disabled it made me think the issue lay within Prometheus. If that's not the case I can open an issue on the kube-state-metrics github instead. There was a change to the openmetrics format in this release kubernetes/kube-state-metrics#1974 which could be related? Seems others have seen this behaviour too prometheus-community/helm-charts#3050.
What did you do?
Upgraded Kube-State Metrics to 2.8.0, enabled native-histogram feature flag on Prometheus
--enable-feature=native-histograms
.What did you expect to see?
Successful scraping of the kube-state-metrics endpoint
What did you see instead? Under which circumstances?
An error of
proto: wrong wireType = 0 for field Metric
when attempting to scrape the kube-state-metrics pod.If native-histograms are disabled this error does not appear and it scrapes correctly as expected.
System information
No response
Prometheus version
Prometheus configuration file
No response
Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response
The text was updated successfully, but these errors were encountered: