-
Notifications
You must be signed in to change notification settings - Fork 501
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
cAdvisor metrics are missing metadata information #867
Comments
With #868, majority of the metrics have regained metadata information. However a lot of filesystem and io related metrics are still missing metadata. (e.g. |
Just expanding on the above comment, our team noticed all of these metrics:
are lacking metadata and some of these are used for autoscaling and other behavior in some of our workloads. |
@baasumo Thanks for following up on this! |
Support for these metrics is still not in cAdvisor upstream, per google/cadvisor#2785 (comment). |
Is there a way we can get labels and annotations from the pod running these containers? |
It appears we were able to improve this slightly with the referenced issue above, but from what I can tell the full fix for this is actually something outside of Botttlerocket. I'm going to close this since we don't have any concrete things identified in Bottlerocket, but feel free to reopen if there is anything else that can be done from this end. |
Image I'm using:
bottlerocket-aws-k8s-1.15-x86_64-0.3.1-8a0c0b3 with a v1.15 EKS control plane
What I expected to happen:
cAdvisor metrics to have associated metadata available (e.g container_name, pod, namespace)
For example,
container_fs_usage_bytes
for an AL2 based EKS node:What actually happened:
cAdvisor metrics all have missing metadata information in an Bottlerocket node.
How to reproduce the problem:
http://localhost:8001/api/v1/nodes/$NODE_NAME/proxy/metrics/cadvisor
Substitute
$NODE_NAME
with the name of a bottlerocket node.The text was updated successfully, but these errors were encountered: