Allow defining versions of metrics / Introduce the concept of "base metric" #1537
siljamardla
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There is often a case when we have multiple versions of the same metric, for example:
or
These are slightly different use cases: for the revenue metric we actually have 4 different underlying columns in the fact table while for the distance metrics we would define the first as a simple metric and the second would be a derived metric on top of the simple metric.
The common annoyance here is that we have to maintain each of these metrics separately, make sure we have some naming convention in place and produce very similar YML. I have even written an article on how I manage these.
I would like there to be some concept of "base metric" that would hold all the common aspects: name, documentation, label etc.
And then we could have additional configurations to define the differences. Maybe something like:
This would automatically create metric versions that I could query:
The labels and documentation would be appended where added etc.
For the second use case with units it might be something like:
These suggestions are not seriously thought through, I'm just trying to put some idea out there.
Might also relate to #1536
Beta Was this translation helpful? Give feedback.
All reactions