graphite-dev team mailing list archive
-
graphite-dev team
-
Mailing list archive
-
Message #04281
Re: [Question #223956]: Graphite-Web Refactoring Help Request
Question #223956 on Graphite changed:
https://answers.launchpad.net/graphite/+question/223956
Dieter P posted a new comment:
> is there still interest?
hell yeah.
> carbon layer (...) and expects each series to be an individual file.
that's a whisper (and maybe ceres) implementation detail. not a carbon
design goal or anything.
In case anyone cares, at work I wrote https://github.com/vimeo/carbon-
tagger ; it's a daemon that sits in (y)our carbon pipeline and maintains
a tag database for all metrics flowing through, it can do this because
the metric id's ("names" if you will) contain tag key/value pairs. with
our dashboard (http://vimeo.github.io/graph-explorer/) we can then do
some interesting things based on the tags.
Personally I think metric identifiers should be 100% key/value pairs;
others seem to find it's better to have a dot string with some
associated key/value tags. Implementing both in graphite-web would
probably get too messy, so maybe it's better to leave that to
specialized dashboards.
--
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.