Hello,
On 4/22/22 14:42, Steve Valliere wrote:
Sorry for being a pest, but I'm trying to figure out what I've done wrong.
After this I promise to shut up and go away. (smile)
Steve, you are very welcome :-), this list has a very low activity,
almost only used for version announcements.
Nowadays, most people seem to prefer GitHub to ask for issues,
questions, etc. Anyway, it's fine to see someone writing here.
I enabled the hourly graphs and got this for the last hour's CPU Core
temperatures (image attached). When I've seen a missing/zero value, there has
always been a (near) vertical line drawn between the X axis and the 'actual'
values. The attached graph doesn't show any of that and yet did not auto scale.
If you look closely, you can see that all five tracks are plotted in the very
narrow 'track blob' at the top.
So, how did I defeat the auto-scaling feature? Or is the graph /using/ a zero
value (that it invented, since 'sensors' never outputs 0C for a CPU Core temp!)
and electing not to draw the associated line segment(s)?
I'm sorry, now I realized that the option 'use_nan_for_missing_data' was
already recently included in the 'lmsens.pm' module. See here
<https://github.com/mikaku/Monitorix/pull/406>.
So you only need to add the following options in your <lmsens> section:
use_nan_for_missing_data = y
limit = 100, 100, 100, 100, 100
and wait until all data plotted (in your selected time frame) is changed
to use NaN for all zero values. That is, your graph will start
autoscaling correctly after an hour in the hourly graph and after a day
in the daily graph and so on.
Check the following issue <https://github.com/mikaku/Monitorix/pull/403>
to read a similar problem a user had but with a different graph.
[Side note: I tried switching to text mode output to look at the values, but all of the
selections I have tried fail with messages like "ERROR: while fetching
/var/lib/monitorix/lmsens.rrd: resolution: value must be (suffixed) positive number"
on the HOURLY setting -- text mode seems to work fine for daily and above]
Yes, text version might well support only standard time frames (daily,
weekly, etc.), hourly is a 'tricky' time frame.
Regards.
--
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat
_______________________________________________
Monitorix-general mailing list
Monitorix-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/monitorix-general
