-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Metrics for SSA cache #10527
Comments
This issue is currently awaiting triage. CAPI contributors will take a look as soon as possible, apply one of the Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
(cc @chrischdi as you showed interest in that topic) |
/kind feature |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
hey @sbueringer id be interested in opening a PR for this - this is still something that would be helpful right? |
Yes, absolutely! Feel free to go ahead /assign @cahillsf |
opened up a draft pr and added some comments whenever you have a chance to take a pass |
A while ago we implemented a ssa.Cache to cache SSA calls. I think it would be great if we have corresponding metrics (e.g. cache hit/miss) so we can observe how well the cache is working.
We should at least have labels for:
I think we'll have to extend the cache a bit to have the data for the labels.
Also let's take a look at how cache metrics usually look like in the Prometheus format and try to be consistent with that.
The text was updated successfully, but these errors were encountered: