Release - August 9th, 2021
#
โจ New โจ#
Average Aggregation TypeDetails
Product Component
Metrics Framework
More Detail
We added the average aggregation type for measures to the framework.
Verification Steps
Specify agg
as average
to use this aggregation type for your measure.
measures: - name: avg_revenue description: Average Revenue expr: revenue_value agg: average
#
Improved Chart TooltipsDetails
Product Component
Metrics Catalog
More Detail
We updated the tooltip on the chart to better portray the given granularity for both weekly and monthly granularities. For week, we now show a range. For month, we show the month and the year.
Verification Steps
- Navigate to a metric that supports granularity and update granularity to weekly (as an example)
- Hover over the chart to show the range
#
๐ Bug Fixes ๐#
Metric Collection Grid LImitDetails
Product Component
Metrics Catalog
More Detail
Our collections page had a bug where if you attempted to add more than five metrics, it would not save the metric onto the collection.
Verification Steps
- Create a collection
- Add more than five metrics to a collection page and confirm it saves properly.
#
Decimal Display IssueDetails
Product Component
Metrics Catalog
More Detail
Fixed a bug where ratio/percentage metric y-axes were showing integers, not decimals.
Verification Steps
Navigate to any ratio and percentage metric to confirm y-axes aren't showing integers.
#
View Code Link in LineageDetails
Product Components
Metrics Catalog
More Detail
The link to View Code
in when you are drilled into the metric lineage would not navigate to the right place, and we want to make sure you can view your code anytime from your metric page!
Verification Steps
This fix requires a new model commit so we can properly grab the path to the code. Once you've committed a new model, go to any metric lineage and click into View Code
at the bottom of the panel. Confirm this takes you to the correct configs in Github.
#
Validation for Time GranularityDetails
Product Component
Metrics Framework
More Detail
We fixed a validation gap in our framework for time granularity. Currently, time_granularity
in our framework only supports the option of day.
We didn't throw an error if you input an unsupported option. We added the correct validation.
Verification Steps
Input an unsupported granularity and confirm that configurations do not validate.