✨ New ✨
We've added a new aggregation type for measures:
boolean. If you have a field thats TRUE/FALSE, you can now use this aggregation type as opposed to creating additional expression logic. This aggregation type will sum true values as 1, 0 otherwise.
- Create a measure from a boolean field and denote
- name: has_reply
description: Denotes if there was a reply to a question.
- Tell a Boolean dad joke, such as "What did the 1 say to the 0?" — "Stop Boolean me!"
🐛 Bug Fixes 🐛
Metric Owner Display Bug
The metric owner was previously not showing up on the main page that shows recently viewed and popular metrics. Among other things, we care a lot about ownership at Transform, so we want to make sure this field was very visible to you and your teams. The metric owner should now show up on the left-hand side of the graph card.
Note that you'll have to first republish your configs for this change to propagate into the UI. Also, in general, you should make sure that the metric owner you've specified in the YAML has an account in the Transform UI.
- Republish your configurations
- Load the metrics dashboard and make sure you see the owners on each respective metric at the bottom of the chart. See the example below
Measures header always plural
In the header to define
measures in a data source, you previously had to use the field
measure if you had only one measure defined. Then, if you added multiple measures later, you were required to make
measure plural to
measures. We thought that was rather silly and also inconsistent with the other objects in the YAML config.
To match the semantic of other fields in the file (e.g.,
identifiers, dimensions ),
measures is now the field to use regardless of how many measures you have.
measures to define a single or multiple measures.
- name: messages
description: The total number of messages sent.
Data Source Capitalization Bug
Previously, if you capitalized the name of a data source, such as the below example, there would be errors when processing the YAML files. Oopsie Daisy. We've fixed this so that names are now case-insensitive.
description: rainfall across all weather stations, starting in Oct 2020.
Create a datasource with a capitalized name and confirm it works.
Remove Version from YAML file
Product Component Metrics Framework
We removed the version from the YAML file because, well frankly, it wasn't used for anything! This applies to the version you find in the metrics YAML as well as your data sources. You no longer need to specify a version in your data sources or metric YAML.
- Create and verify a config without the version field
- Say "you're welcome" to your fingers because they can type less when creating configs.