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)
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)? [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] -----Original Message----- From: Jordi Sanfeliu via Monitorix-general <monitorix-general@lists.sourceforge.net> Sent: Friday, April 22, 2022 3:54 AM To: monitorix-general@lists.sourceforge.net Cc: Jordi Sanfeliu <jo...@fibranet.cat> Subject: Re: [Monitorix-general] lmsensors configuration Hello, On 4/21/22 20:08, Steve Valliere wrote: > Re #2 (setting Y-axis ranges)... I do not understand the need to add the use > nan setting, since to set a sensible range for the bulk of the values on my > graph. For example, the core (and GPU) temps on my system are just about > always 55C +/- 2C, so why am I required to have a graph whose scale goes from > 0 to 60? I was hoping it might auto-adjust the low limit on the scale once > the graph filled, but it did not. > It looks like both the min and max values for the Y axis are settable > parameters for the graphics package, so I'm requesting that we be allowed to > set them without hacking into the perl script on our own. But I think I can > figure that out if you don't think there's any value to graphs that aren't > generally a flat line, um, sorry, I mean if you don't see the value in this > option. > The graphs do autoscaling automatically, this is an RRDtool feature. The problem is that some graphs plot a zero value when there is not value to plot and that forces the graph to scale from 0 to the maximum value represented. This behavior is accepted in the majority of cases. That's the reason why not all the graphs include the option 'use_nan_for_missing_data' which forces to use the value NaN when there is no value to represent. 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
_______________________________________________ Monitorix-general mailing list Monitorix-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monitorix-general
