graphite-dev team mailing list archive

[AcidTonic <question99926@xxxxxxxxxxxxxxxxxxxxx>]

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

AcidTonic gave more information on the question:
Can I reorganize .wsp files by moving them and sending data to the new
location?

Is there anything already developed around sorting incoming data in some
way....  Such as handling machines that move or change hostnames? I'd like
to move the data to the new spot when the hostname or ip changes. Honoring
the new hostnames regex in the schemas.conf. Data would be moved but reduced
to the precision of the new names schema match, then new data would go there
as usual as if it never moved.

I also wish to trap the create event so I can make django database rows for
the new device and trigger any alerts. I see I could use the api you sent
previously to recurse through the datapoints looking for new ones but it
would be much more efficient to be notified resource wise.

Any thoughts?


On Fri, Feb 12, 2010 at 1:03 PM, AcidTonic <
question99926@xxxxxxxxxxxxxxxxxxxxx> wrote:

> Your question #99926 on Graphite changed:
> https://answers.launchpad.net/graphite/+question/99926
>
> You gave more information on the question:
> I would be happy to release it. Even though I'm writing something that will
> be closed with a possible open source foundation, I plan to release all
> additions to 3rd party tools/libraries to the owners back under their
> license terms.
>
> It's the least I can do....
>
> On Fri, Feb 12, 2010 at 12:35 AM, chrismd <
> question99926@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
> > Your 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.
> >
> > --
> > If this answers your question, please go to the following page to let us
> > know that it is solved:
> >
> >
> https://answers.launchpad.net/graphite/+question/99926/+confirm?answer_id=12
> >
> > If you still need help, you can reply to this email or go to the
> > following page to enter your feedback:
> > https://answers.launchpad.net/graphite/+question/99926
> >
> > You received this question notification because you are a direct
> > subscriber of the question.
> >
>
> --
> You received this question notification because you are a direct
> subscriber of the question.
>

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