Careful about installing Influxdb and Telegraf on the same system via RPM (maybe DEB too), they both share common paths and filenames, and cause one (or the other) not to start.<p><a href="https://github.com/influxdb/telegraf/issues/22" rel="nofollow">https://github.com/influxdb/telegraf/issues/22</a>
<a href="https://github.com/influxdb/influxdb/issues/3123" rel="nofollow">https://github.com/influxdb/influxdb/issues/3123</a><p>Also, the changelog items for telegraf all point at influxdb issues.<p><a href="https://github.com/influxdb/telegraf/blob/master/CHANGELOG.md#v012-2015-07-01" rel="nofollow">https://github.com/influxdb/telegraf/blob/master/CHANGELOG.m...</a><p>I am really excited about telegraf, but am worried about long term maintenance of yet another stats collector. It is very easy to setup, and seems like it will be quiet easy to extend.
"Some users logged issues about a large number of IOPS during heavy write loads. To address this we implemented a write ahead log, or WAL. No migration is required to take advantage of this feature and it is available as soon as you upgrade. It’s worth noting here that if you are testing a high write load scenario, you will get occasional pauses of up to 3 seconds during WAL flushes (depending on hardware and schema). Set your timeouts accordingly. We’ll work on smoothing this out over time in future 0.9 point releases."<p>This is a pretty major change and a big caveat!
I'd love it if you could comment on how InfluxDB + Telegraf + Grafana + $OpenSourceAlertingTool compares to commercial offerings like DataDog or SignalFx?<p>Also, is Telegraf meant to replace cAdvisor for InfluxDB users?