4 ms·

I have just shut down 95% of my collectd/graphite infrastructure after migrating it over to InfluxDB+telegraf+grafana. I'm loving it! Since shutting down coll

I have just shut down 95% of my collectd/graphite infrastructure after migrating it over to InfluxDB+telegraf+grafana. I'm loving it! Since shutting down collectd, system load and io wait time across my fleet has gone way down, and available CPU has gone way up. Though I wouldn't say it was a smooth transition. I started with 0.8, IIRC, and while it worked ok it used an amazing amount of storage. 4GB for a year worth of graphite data blew up to 100GB for a month of InfluxDB. I gave up on InfluxDB a few times during the process, but at 0.11 I tried it again and is has been pretty good. We are only putting the Telegraf data and one small service statistic in it, but the storage is pretty reasonable at 12GB for a few months of data. Querying and graphing the data with Grafana is great. If you have tried it before 0.11, definitely try it again. The guys giving a Prometheus talk at PyCon were really down on InfluxDB, but they hadn't tried it for 6 months. I was like "Yeah, it was unusable then". I wanted to like Prometheus, but I just couldn't figure out how to feed my data into it.

el_isma 10y ago
Have you tried 0.13? How much disk space is it using? It's supposed to be "better than graphite". Really curious as I am looking forward to set up InfluxDB (moving from graphite too). I was going to use collectd, but your comment makes me wonder if it's the right choice.
- linsomniac 10y ago
  Yeah, I'm currently running 0.13.0. It's really hard to compare and say better or worse than graphite, because it isn't an apples/apples comparison. I, so far, haven't figured out how to do roll up like graphite has built in, so I think I'm holding onto the high precision data. So that makes it not even close to a fair comparison. Still though, 12GB for our current data set feels reasonable. Back in 0.8 when it was more like 150GB for a month, that was not gonna work. For a while I was feeding collectd into InfluxDB. It didn't really produce anything I could use immediately, and I haven't gone back to revisit it.

el_isma 10y ago

Have you tried 0.13? How much disk space is it using? It's supposed to be "better than graphite". Really curious as I am looking forward to set up InfluxDB (moving from graphite too). I was going to use collectd, but your comment makes me wonder if it's the right choice.

linsomniac 10y ago
Yeah, I'm currently running 0.13.0. It's really hard to compare and say better or worse than graphite, because it isn't an apples/apples comparison. I, so far, haven't figured out how to do roll up like graphite has built in, so I think I'm holding onto the high precision data. So that makes it not even close to a fair comparison. Still though, 12GB for our current data set feels reasonable. Back in 0.8 when it was more like 150GB for a month, that was not gonna work. For a while I was feeding collectd into InfluxDB. It didn't really produce anything I could use immediately, and I haven't gone back to revisit it.