-
Notifications
You must be signed in to change notification settings - Fork 63
fix: In Client-side metrics makes sure that the right views get created for the right metrics #1590
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
Conversation
…ed for the right metrics
…pis/nodejs-bigtable into 359913994-views-change-2
@@ -97,7 +97,7 @@ function createInstruments(exporter: PushMetricExporter): MetricsInstruments { | |||
new View({ | |||
instrumentName: name, | |||
name, | |||
aggregation: name.endsWith('latencies') | |||
aggregation: !name.endsWith('latencies') |
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.
should there be a test verifying this?
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.
Sure. I don't want that to block a change to fix something we currently have in production though so I have put this in a backlog bug. Verifying the views got created is fairly non-trivial.
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.
LGTM, but consider a test so this can't slip through in the future
Description
This is a one line fix. If the aggregation ends with 'latencies' then the explicit bucket histogram should be used, not the sum histogram and vice versa.