When you have large volumes, disk1 is the better view. 99% can still a significant amount so looking at usage vs percentage is much more relevant.
=G=
From: Xymon <xymon-bounces at xymon.com> on behalf of Jeremy Ruffer <user-6d8e227afca3@xymon.invalid>
Sent: Wednesday, August 30, 2017 11:38 AM
To: Robert Herron
Cc: xymon Mailing List
Subject: Re: [Xymon] Human readable disk space
EXTERNAL
I'm afraid that I don't know, we don't use disk1.
Jeremy Ruffer
On 30 August 2017 at 15:33, Robert Herron <user-8b27ea4290da@xymon.invalid<mailto:user-8b27ea4290da@xymon.invalid>> wrote:
What does it do to the "Disk Usage" (aka disk1) graphs?
disk = "Disk Utilization (% full)"
disk1 = "Disk Usage (bytes)
On Aug 30, 2017 5:48 AM, "Jeremy Ruffer" <user-6d8e227afca3@xymon.invalid<mailto:user-6d8e227afca3@xymon.invalid>> wrote:
I hacked xymonclient-linux.sh and changed k to G, I think. It actually took me a while to work out what I had changed.
This doesn't affect the graph which goes by percentage.
HTH
Jeremy Ruffer
On 30 August 2017 at 10:35, Richard Hamilton <user-af55987f6d56@xymon.invalid<mailto:user-af55987f6d56@xymon.invalid>> wrote:
Just at a guess, one could easily enough change the client-side scripts, but that would break the graphs, which probably need unscaled numbers. Even if the graphing could have the ability to understand scaled numbers, that would introduce rounding errors (sort of a staircase effect on the graph) proportional to the scale in use for a particular number.
In principle, I guess the report could have one part that's human-readable, and another part that's used for the graphs. How feasible that is, I'll leave to someone else to answer.
On Wed, Aug 30, 2017 at 4:27 AM, Steffan <user-a2c231b1253e@xymon.invalid<mailto:user-a2c231b1253e@xymon.invalid>> wrote:
Hello List,
Im using xymon for many years
I just wondering is there a easy way to make the output more readable?
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/mapper/sysvg-root 10321208 4397592 5399328 45% /
/dev/sda1 1032088 152244 827416 16% /boot
/dev/mapper/sysvg-vz 1898719656 249544968 1552725360 14% /vz
As you see there is no scaling in the output to GB etc
Thanxs
Steffan