bpaquet / collectd-influxdb-proxy Goto Github PK

I've found that when using the collectd-influxdb-proxy as described in the readme, I eventually stop seeing metrics show up in InfluxDB.

I'm collecting 4 JMX metrics from a single JVM on a 15 second interval with collectd's GenericJMX plugin. When watching the data via Grafana or InfluxDB's admin interface, after a minute or two I stop getting metrics. Bouncing the proxy resolves the issue. As a hacky workaround I have a cron job restarting the proxy every 60 seconds, and I'm able to retain my 15-second resolution this way.

Interestingly, the verbose output from the proxy still shows that it is pushing each individual metric to InfluxDB whenever collectd's write-http plugin flushes its buffer, but the metrics don't necessarily make it into Influx.

I believe I've confirmed that it is indeed the proxy that is the point of failure by experimenting with different restart intervals on the cron job. When it's set to restart every 5 minutes, I get full resolution metrics for anywhere from 1.5 to 3 minutes, then the metrics flatline until the next restart of the proxy. Shrinking this interval to 3 minutes yields more consistent metrics, but there are still gaps of up to 1.5 minutes in the metrics.

Setting it to a 1 minute restart interval via cron yields mostly consistent full-resolution metrics, but there are still occasional spots where there is a 30-second jump gap between values.

What is the advantage of using your proxy instead of the combo collectd + InfluxDB [input_plugins.graphite] ?

Hi,

Load plugin seems to be not forwarded to influxdb

If you have an idea ...

Regards,

Cyril

Need to add note to run npm install in readme, else the following happens:

# node proxy.js 

module.js:340
    throw err;
          ^
Error: Cannot find module 'optimist'