Graphite

Question about Graphite and long term storage

Asked by PC

We have a lot of data (possibly years worth of minute data) and are thinking of using Graphite to display adhoc queries from this dataset.

Apologies, I could not find the information needed to answer this question in the FAQ or documentation or architecture diagram.

Is it viable to use Graphite in this way? The usage pattern would be:

1. User constructs their query
2. Our application sends the data to Graphite which displays it

I notice in the documentation that one needs to specify schemas ahead of time, so perhaps the above is totally not in keeping with how Graphite is meant to be used.

We'd be managing the long-term storage of our data separately and using Graphite's data storage only as a "cache".

If there exists other examples or documentation I'm happy to read that too if someone can point me to it?

Also, does graphite provide any sort of user interface for editing data in its database? eg. select a section, zoom into it, edit one point.

Many thanks,

PC

Question information

Language:
English Edit question
Status:
Solved
For:
Graphite Edit question
Assignee:
No assignee Edit question
Solved by:
chrismd
Solved:
Last query:
Last reply:
Revision history for this message
Best chrismd (chrismd) said : 		#1

Currently there is no way to include data points in the rendering request, they must be sent to the backend prior to the rendering request, but that would not be a very hard feature to add. Since graphite only renders data that is stored in its database, so the usage pattern (for now) would need to be to first import all the data you users may want to query, then they can view it through the web interface.

Also Graphite does not support editing of data through the web interface, the only way to write to Graphite's database is through the backend API.

Revision history for this message
PC (corno) said : 		#2

Thank you!