-
Notifications
You must be signed in to change notification settings - Fork 179
Add metric about metrics freshness #126
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
Add metric about metrics freshness #126
Conversation
@olivierlemasle: This issue is currently awaiting triage. If custom-metrics-apiserver contributors determine this is a relevant issue, they will accept it by applying the 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. |
ac0e2c8
to
aacfcf3
Compare
I've updated the PR to follow your suggestions. |
aacfcf3
to
aabcc02
Compare
In test-adapter, the timestamp for custom metrics values is currently the time when the metric is queried. With this change, the timestamp used is the time when the metric value is created / updated.
aabcc02
to
caacb02
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes related to the new metrics looks good to me, but the ones in the test-adapter provider need to be reflected in https://github.com/kubernetes-sigs/custom-metrics-apiserver/blob/master/docs/getting-started.md. That can be done in a follow-up but we need to make sure that we keep the doc up-to-date.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dgrisonnet, olivierlemasle The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Yes, I'm thinking about it since #108. I've just opened an issue for that topic: #132. |
@olivierlemasle @dgrisonnet would be nice to have all exposed metrics documented somewhere. |
I opened an issue to keep track of that: #134 |
Add a metric
custom_metrics_apiserver_metric_freshness_seconds
, similar to the metricmetrics_server_api_metric_freshness_seconds
from metrics-server.This metric can optionally be registered using
RegisterMetrics(registrationFunc func(metrics.Registerable) error) error
, e.g:Also, in test-adapter:
custom_metrics_apiserver_metric_freshness_seconds
;