-
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
Custom resources spam Info metric %s does not have _info suffix
#2155
Labels
kind/bug
Categorizes issue or PR as related to a bug.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
k8s-ci-robot
added
the
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
label
Aug 18, 2023
/triage accepted
|
k8s-ci-robot
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Aug 18, 2023
We could move the name validation and log output somewhere into kube-state-metrics/pkg/customresourcestate/registry_factory.go Lines 72 to 97 in 64c05ae
|
chrischdi
changed the title
Custom resources spam
Custom resources spam `Info metric %s does not have _info suffix
Aug 18, 2023
Info metric %s does not have _info suffix
for metrics similar to core APIs
chrischdi
changed the title
Custom resources spam `Info metric %s does not have _info suffix
Custom resources spam Aug 18, 2023
Info metric %s does not have _info suffix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Categorizes issue or PR as related to a bug.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What happened:
I configured a custom resource metric with the following configuration:
KSM spams the following message on every CR creation:
This is caused here:
kube-state-metrics/pkg/metric_generator/generator.go
Line 79 in 64c05ae
What you expected to happen:
Infof
or properly usingInfoS
, e.g.klog.InfoS("Info metric does not have _info suffix", "family.Name", family.Name)
How to reproduce it (as minimally and precisely as possible):
Use the above configuration and adjust to any kind of custom resource (because all provide the
.metadata.ownerReferences
property)Anything else we need to know?:
Environment:
kubectl version
): v1.27.3The text was updated successfully, but these errors were encountered: