I'm testing nmon2influxdb to get metrics of some devices.
I have set up a simple bash script on cron.d that runs every minute with the following command on 2 different host:
/opt/nmon2influxdb/nmon2influxdb import <HOST1>:<PATH>/nmon/HOST_YYMMDD_0000.nmon/opt/nmon2influxdb/nmon2influxdb import <HOST2>:<PATH>/nmon/HOST_YYMMDD_0000.nmon
As I have seen, when the checksum of the file changes (every 1 minute) and aparently all points (older than now and the new ones) on the file are sent permanently. So a question rises up:
Shouldn't the nmon2influx check only for the new points?
Plus info:
The points are written OK to InfluxDB, with no apparently issues.
The checksum/timestamp measurements are writteng and aparently read OK to/from InfluxDB.
Hi! First of all, thanks for that great tool!
I'm testing nmon2influxdb to get metrics of some devices. I have set up a simple bash script on cron.d that runs every minute with the following command on 2 different host:
/opt/nmon2influxdb/nmon2influxdb import <HOST1>:<PATH>/nmon/HOST_YYMMDD_0000.nmon
/opt/nmon2influxdb/nmon2influxdb import <HOST2>:<PATH>/nmon/HOST_YYMMDD_0000.nmon
As I have seen, when the checksum of the file changes (every 1 minute) and aparently all points (older than now and the new ones) on the file are sent permanently. So a question rises up:
Plus info: