Skip to content
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

[Feature] Add new config to metric definition to specify positive direction #1587

Open
3 tasks done
siljamardla opened this issue Dec 30, 2024 · 0 comments
Open
3 tasks done
Labels
enhancement New feature or request triage Tasks that need to be triaged

Comments

@siljamardla
Copy link

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing metricflow functionality, rather than a Big Idea better suited to a discussion

Describe the feature

We use metric definitions in different contexts. For many of them, a common requirement is to help the user understand what's good and what's bad. e.g. for a revenue metric good is going up, bad is going down while for a cost metric good is going down while bad is going up.
It would be good to specify the positive direction of a metric right in the definition of a metric. This could then be picked up and used in reporting, experimentation etc.

Describe alternatives you've considered

Specifying the direction on consumer side (possibly in multiple places, adding overhead).

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

@siljamardla siljamardla added enhancement New feature or request triage Tasks that need to be triaged labels Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage Tasks that need to be triaged
Projects
None yet
Development

No branches or pull requests

1 participant