Skip to content

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

Open

Description

@DStape

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions