-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Rename metric name for request latency in feast serving #488
Rename metric name for request latency in feast serving #488
Conversation
So that it is consistent with the actual unit of timing being measured And recommended metric names in Prometheus https://prometheus.io/docs/practices/naming/#metric-names
/retest |
1 similar comment
/retest |
/hold |
Test fails because several hours ago
with this error
2 potential fixes:
- time_offset = datetime.utcnow().replace(tzinfo=pytz.utc)
+ time_offset = datetime.utcnow().replace(tzinfo=None) |
/retest |
74be918
to
3e5be55
Compare
Can we merge this @davidheryanto ? |
/hold cancel |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davidheryanto, woop 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 |
So that it is consistent with the actual unit of timing being measured And recommended metric names in Prometheus https://prometheus.io/docs/practices/naming/#metric-names (cherry picked from commit 5758d99)
So that it is consistent with the actual unit of timing being measured And recommended metric names in Prometheus https://prometheus.io/docs/practices/naming/#metric-names (cherry picked from commit 5758d99)
What this PR does / why we need it:
So that it is consistent with the actual unit of timing being measured.
And recommended metric names in Prometheus https://prometheus.io/docs/practices/naming/#metric-names
Which issue(s) this PR fixes:
NONE
Does this PR introduce a user-facing change?: