Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes a couple of issues from initial latency PR.
Latency Units
Latencies were exported in microseconds, so the values fell outside of all buckets for histogram. Latencies are still recorded in microseconds, but exported in float64 milliseconds.
Example of current data from prod:
Example from local testing with updated units:
After this update, a dash to show the distribution of latency values will be possible. Currently, we can only see a mean and that all values are less than infinity.
metric.go
UpdatesExportLatencyMetrics
was refactored to be more readable. It performs the same function, but in a way where someone that isn't me can tell what is going on. The initial version was a confusing mess of maps (sorry). The unit tests were updated to match the changes as well.