Vigor165 plotting some graphs not working about vigor130 HOT 3 CLOSED

That is because these are different types of values, in the case of e.g. data rate what the modem reports already is the current rate and munin does no further processing of that value because there is no need, while for e.g. CRC-errors what the modem reports is just a counter that increases with every error, and it's munins job to figure out on its own how much it changes over time. These types are 'gauge' vs 'derive' in munin or rrdtool speak. You can see which is which either by looking at the sourcecode; by running the plugin with the parameter 'config'; or in the munin webinterface by clicking a graph: below the graph there will be a table, and there is a column 'type'.

from vigor130.

I'm not sure there even is anything to fix, my gut feeling tells me this might just be a misunderstanding?
What you see when you run the script manually is what the vigor returns, which in the case of CRC errors is the total number of CRC errors that have occoured since you booted the Vigor. That however is not what munin draws, what munin draws is how much new errors have occoured since the last run (with runs usually occouring every 5 minutes). If you run the plugin manually 5 minutes apart and the CRC numbers do not increase between these two runs, then it's absolutely correct that munin draws a "0" for that interval, simply because no CRC errors have occoured in that interval.

from vigor130.

@poempelfox , well, that would be a good explanation.
However, other values / graphs, e.g. SNR Attentuation or Data Rate are plotting exactly the values as reported when I run the script manually.

So I will wait a few days to see if errors graph is changing.
Thanks for chiming in here.

from vigor130.