graphite-dev team mailing list archive

[chrismd <question99926@xxxxxxxxxxxxxxxxxxxxx>]

Question #99926 on Graphite changed:
https://answers.launchpad.net/graphite/+question/99926

    Status: Open => Answered

chrismd proposed the following answer:
Unfortunately no the Store API doesn't let you iterate everything
currently. There are a few ways you could go about doing that, os.walk,
Store.find('*') + Store.find('*.*') + ..., or better yet just use the
index file. So yet another undocumented feature is that there is a
script in graphite trunk, misc/rebuild_index.sh. Edit it to specify your
graphite installation location then run it and it will generate a file
$GRAPHITE_ROOT/storage/index that will be a simple text listing of all
of your metrics. That would probably be the cheapest way to iterate
everything, assuming your data doesn't change often or you rebuild the
index often. You can easily lookup the index file in your code by using
the INDEX_FILE setting.

With metric.fetch() however there is a simple way to fetch everything,
simply specify a startTime of 0 and an endTime of time.time(). You can
also directly use the whisper.fetch() library call the same way if you
don't end up using the Store API.

As for your new Ext UI, I've made many different UI's for graphite using
Ext and it is pretty straight forward. One bit of code you might find
useful to borrow from Graphite is the ParameterizedURL prototype defined
in webapp/content/js/composer.js. It gives you simple methods for
manipulating your graph's url parameters.

I've been thinking about redoing Graphite's Composer UI myself lately,
I've made some other UI's on another project that I think work better.
So I would definitely be interested in seeing what you come up with if
you are at liberty to release it.

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.