-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated Prometheus metrics output not meet with the requirements #2366
Comments
I've tested the flux2-monitoring-example and verified we were using kube-state-metrics v2.12.0, it does not seem to resolve the issue completely, though some metrics came back, in fluxcd/flux2-monitoring-example#32 you can see we only returned "HelmRelease" metrics and the other resource kinds' metrics did not come back. |
I did some tests and found, that it's related to the code change of the The issue seems to be in the I am just not sure if that's a bug or a feature, maybe the author @rexagod knows? |
/assign @CatherineF-dev |
I can confirm. After I changed the "help" fields, the metrics are appeared in Prometheus and Grafana. Thanks @speer ! |
Hello, apologies for the late response. 👋🏼 Prometheus' protobuf machinery does not support all OpenMetrics types at the moment (#2248). To resolve this, #2270 was merged which implicitly converted fluxcd/flux2-monitoring-example#32 (comment) presents a take on this that has been the implicit sentiment on such configuration scenarios, i.e., if the use-case warrants for different I'd be happy to follow this up by pointing out the caveat observed here in the documentation for future instances. |
Hello, Many thanks for the detailed explanation. It's clear now, why it caused the issue. 👍️ |
What happened:
The KSM configuration worked well until KSM version v2.10.1. After the upgrade to v2.11.0 the Prometheus reported "invalid metric type" error message. The latest version v2.12.0 solved the "invalid metric type issue", but the required output has been provided only one resource type per metrics. The deployment and configuration not changed during this period.
The issue affected with the "build_info" metric name.
What you expected to happen:
To provide Prometheus output with same metric name and more resource type.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
): 1.28.5The text was updated successfully, but these errors were encountered: