Graphite

What are plans for Ceres, Whisper fork, etc.?

Asked by Mary-Anne Wolf

I earlier said "As you may know, Graph-Explorer forked off its own version of Whisper in order to add tags to metrics and to integrate a Lucene (ElasticSearch) Search." It turns out that is incorrect.

Also, Grafana has the ability to get its information from both Grafite and Influxdb.

The Ceres and Whisper git repositories have not been touched in months.

What is the plan for how the storage of metrics will evolve in Graphite? What is the expected timeframe for doing this?

What is the plan for improving how Dashboards are made and how the metrics in them are found? What is the expected timeframe for doing this?

Thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
Graphite Edit question
Assignee:
No assignee Edit question
Solved by:
Mary-Anne Wolf
Solved:
Last query:
Last reply:
Revision history for this message
Dieter P (dieter-plaetinck) said : 		#1

> As you may know, Graph-Explorer forked off its own version of Whisper in order to add tags to metrics and to integrate a Lucene (ElasticSearch) Search.

this is not true. Graph Explorer uses graphite (or graphite-ng) and whatever backend your graphite/graphite-ng is using. It uses elasticsearch as an index of metric identifiers along with their tags, but it doesn't concern itself with how or where your datapoints are stored.

see https://github.com/vimeo/graph-explorer/wiki/Relationship-between-Graph-Explorer,-Graphite,-Elasticsearch-and-Carbon-tagger for more information

Revision history for this message
Mary-Anne Wolf (mgwmgw) said : 		#3

Thanks to Dieter's correction, which pointed me to a website that mentioned graphite-ng, I now know where the evolution of storage for graphite is happening. According to
https://github.com/graphite-ng/graphite-ng
there are multiple stores supported, but the recommended one is
https://code.google.com/p/kairosdb/

Thanks, Dieter!

Revision history for this message
Dieter P (dieter-plaetinck) said : 		#4

note that graphite-ng's api is currently nowhere near as featurefull as graphite's is.
Graphite recently got support for multiple backends as well and it wouldn't suprise me if it gets support for kairos, influx and others soon.

Revision history for this message
Mary-Anne Wolf (mgwmgw) said : 		#5

In case anyone is wondering, here is an early post about the relationship between graphite and graphite-ng.
http://dieter.plaetinck.be/graphite-ng_a-next-gen-graphite-server-in-go.html