-
Notifications
You must be signed in to change notification settings - Fork 98
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
Use MetricTimeDefaultGranularityPattern
to resolve metric_time
granularity
#1332
Conversation
7ba1065
to
8cdb31f
Compare
8e2d601
to
2a0bcb2
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 look good, but I am wondering about the behavior change for how the default now allows for what was previously an error condition. From what I remember, we wanted to error out to make it easier to see from the configs what the granularity for a time dimension was. Has that thought changed from the product side?
@plypaul this is my understanding of the behavior change (mentioned in the PR description!). This scenario occurs if you query multiple metrics or a derived metric with different
|
These reflect a behavior change in which we don't error if metric_time is queried for metrics with two different default granularities. Instead, we choose the larger of the two, which is guaranteed to work for both metrics.
2a0bcb2
to
425080e
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.
This behavior change was agreed upon by product.
That's what I was inquiring about. Thanks!
Resolve metric time using new spec pattern in group by and filter nodes. This is a change from defaulting to the minimum time granularity for
metric_time
. Now we will use the max default granularity for the requested metrics.Note the snapshot updates. These reflect another behavior change in which we don't error if
metric_time
is queried for metrics with two different default granularities. Instead, we choose the larger of the two, which is guaranteed to work for both metrics.