I am having few difficulties with libreNMS and I am desperate for help.
Its been multiple times that I have evidenced a wrong record in the billing DB (Photos attached) I noticed one spike in usage which seems unreliable. Digging into the traffic graphs, records and DB it was found that the record is from one specific polling cycle (5min). The strange part for me is that we still have a legacy Observium still polling and it does not get that value. I checked the code and it seems the
in_deltavariable is getting through three different conditionals which I assume is the one that involves an actual
snmp_get()to the device and later rests the previous polling value to calculate the actual delta -->
$port_data['in_delta'] = ($port_data['in_measurement'] - $port_data['last_in_measurement']);. that leads me to think is the actual value polled by from the device…but have not been able to prove it… I just got lost at that stage and I have not been able to find out the root cause and solution. Do you guys have any suggestion? How can I trace that polling cycle? which log would be relevant to check? any ideas??.
Other issue I noticed is that the billing cycle, even thought the timestamps are fine. The GUI graphs does not refresh/rollover on the first of the month but it does on the second. How can I change that?. For some reason that is messing with a customize script in production which poll from LibreNMS billing data…that only happens on the first of each month.
I hope you can shed some light on this.