InfluxDB – Open-source distributed time-series, events, and metrics database
1–10 of 79 posts
Re: InfluxDB – Open-source distributed time-series, events, and metrics database
#2I'm one of the committers. The project is still early stage. At this point we're looking for feedback on the API, which we're planning on finalizing this month. Would love to hear about anything you'd like changed or added to the API.
Re: InfluxDB – Open-source distributed time-series, events, and metrics database
#3Very cool, I actually made a basic version of this (only implemented increment) with Go for the same reasons, just drop it on a server and run it.
My implementation would output a chart given parameters:
/chart.png?metric=whatever&time=12h&interval=10m
Are there any plans for easy output of graphs?
Re: InfluxDB – Open-source distributed time-series, events, and metrics database
#4Can't wait to use it. Loving all these new DBs written in Go.
Re: InfluxDB – Open-source distributed time-series, events, and metrics database
#5Very cool, I actually made a basic version of this (only implemented increment) with Go for the same reasons, just drop it on a server and run it. My implementation would output a chart given parameters: /chart.png?metric=whatever&time=12h&interval=10m Are there any plans for easy output of graphs?
We'd definitely like to do that soon. That's one of the really nice things about Graphite and it makes it easy to share in emails, chat rooms, etc. For the moment we're focused on the other parts of the API and building out the clustering part of it.
Re: InfluxDB – Open-source distributed time-series, events, and metrics database
#6This looks like the exact feature-set we need at my company; we're in the middle of moving to Redshift but I'll be keeping an eye on Influx.
I know it's early days but I didn't see any information about cluster management - how does one setup an Influx cluster, can it be resized, what kind of hardware does it prefer?
Re: InfluxDB – Open-source distributed time-series, events, and metrics database
#7sounds interesting; i am currently using hbase for similar purposes. Do "tables" have to be created explicitly, or can I just store a value into a timeseries, and if the ts doesn't exist yet it will be created?
Re: InfluxDB – Open-source distributed time-series, events, and metrics database
#8[deleted]
Re: InfluxDB – Open-source distributed time-series, events, and metrics database
#9I'm one of the committers. The project is still early stage. At this point we're looking for feedback on the API, which we're planning on finalizing this month. Would love to hear about anything you'd like changed or added to the API.
I wouldn't use this bastardized SQL dialect. SQL comes from relational databases, which comes from relational algebra, which is an exceptionally poor model for time series data. It's going to end up a mess and confuse people. SQL is already a mess by itself.
I would simply use functions and operators over time series or data frame types. Perhaps take a look at the R zoo library for examples of more advanced things people do with time series.
Re: InfluxDB – Open-source distributed time-series, events, and metrics database
#10I was actually looking at a bunch of open source time series databases and settled on kairosdb but this looks pretty nice.
I think there is a hackernews rule someplace that a more interesting tech alternative shows up right when you decided to go with something else.
For reference here is the list I created when researching these:
http://opentsdb.net/overview.html Built on HBASE
http://www.gocircuit.org/vena.html Built on go + go'circult uses google's leveldb
https://code.google.com/p/kairosdb/ A rewrite of opentsdb which can use Cassandra
http://blueflood.io/ Built by Rackspace, decent but still seems a bit immature
http://graphite.wikidot.com/ Obligatory Graphite reference (uses whisper, new backend called 'ceres' is being developed)
https://github.com/agoragames/kairos (yet another 'kairos', alternative backends for graphite - SQL, redis, or mongo)
Riak seems to be popular with SASS metric providers (hosted graphite, boundary). There isn’t any code but there are a couple of talks that explain how and why they went with Riak:
http://basho.com/hosted-graphite-uses-riak-to-store-all-cust... http://boundary.com/blog/tag/tech-talks/