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

Why must metric values be ints||floats? #668

Open
DStape opened this issue Aug 3, 2017 · 0 comments
Open

Why must metric values be ints||floats? #668

DStape opened this issue Aug 3, 2017 · 0 comments

Comments

@DStape
Copy link
Contributor

DStape commented Aug 3, 2017

Hello,

I've searched in various places and looked at the commit logs and can't find any satisfactory answer to this question: why does Diamond constrain Metric.value to an int||float? What's the reason behind this? Is it simply due to historical reasons, i.e. Diamond was originally developed alongside Graphite? Is it possible to extend the allowed types to include 'string' as well? (I do understand that string type isn't suitable for apps backed by time-series databases).

Thanks,
David

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant