-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[receiver/redis] Seconds as unit for redis.cmd.latency metric. #26686
[receiver/redis] Seconds as unit for redis.cmd.latency metric. #26686
Conversation
This is a folow-up to PR #26569, so it can skip the changelog. |
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.
Just confirming the latency metrics have not been published in a release yet? Otherwise this would be a breaking change
@codeboten Not to my knowledge. The PR that introduced latency metrics has been merged recently. This PR is a response to #26569 (comment). |
I confirmed new metrics were merged yesterday, and have not been released yet. |
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.
Thanks for confirming @bjandras @crobert-1
…telemetry#26686) Changed unit for `redis.cmd.latency` metric from microseconds to seconds. open-telemetry#6942 Co-authored-by: Alex Boten <aboten@lightstep.com>
Description: Changed unit for
redis.cmd.latency
metric from microseconds to seconds.Link to tracking Issue: #6942