Human readable disk space
list Steffan Noord
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
list Steffan Noord
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
list Richard Hamilton
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> 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
list Jeremy Ruffer
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> 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> 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
list Robert Herron
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> 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> 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> 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
list Jeremy Ruffer
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> 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> 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> 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> 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
list Galen Johnson
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
list Steffan Noord
@ Robert Im sorry yoy lost me Where do you mean? @jerremy Would you like to share the file with me?
▸
Van: Xymon [mailto:xymon-bounces at xymon.com] Namens Robert Herron
Verzonden: woensdag 30 augustus 2017 16:34
Aan: xymon Mailing List <xymon at xymon.com>
Onderwerp: Re: [Xymon] Human readable disk space
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" < <mailto:user-6d8e227afca3@xymon.invalid> 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 < <mailto:user-af55987f6d56@xymon.invalid> 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 < <mailto:user-a2c231b1253e@xymon.invalid> 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
<mailto:Xymon at xymon.com> Xymon at xymon.com
list Jeremy Ruffer
The altered line is line 50
▸
On 31 August 2017 at 10:07, Steffan <user-a2c231b1253e@xymon.invalid> wrote:
@ Robert Im sorry yoy lost me Where do you mean? @jerremy Would you like to share the file with me? *Van:* Xymon [mailto:xymon-bounces at xymon.com] *Namens *Robert Herron *Verzonden:* woensdag 30 augustus 2017 16:34 *Aan:* xymon Mailing List <xymon at xymon.com> *Onderwerp:* Re: [Xymon] Human readable disk space 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> 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> 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> 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
Attachments (1)
list Steffan Noord
If i look at line 50 i see
df -Pl -x iso9660 -x $EXCLUDES | sed -e '/^[^ ][^ ]*$/{
I changed it to
df -Plh -x iso9660 -x $EXCLUDES | sed -e '/^[^ ][^ ]*$/{
that works
to bad I have to go trough all servers…
▸
Van: Jeremy Ruffer [mailto:user-6d8e227afca3@xymon.invalid]
Verzonden: donderdag 31 augustus 2017 11:32
Aan: Steffan <user-a2c231b1253e@xymon.invalid>
CC: xymon Mailing List <xymon at xymon.com>
Onderwerp: Re: [Xymon] Human readable disk space
The altered line is line 50
On 31 August 2017 at 10:07, Steffan < <mailto:user-a2c231b1253e@xymon.invalid> user-a2c231b1253e@xymon.invalid> wrote:
@ Robert
Im sorry yoy lost me
Where do you mean?
@jerremy
Would you like to share the file with me?
Van: Xymon [mailto: <mailto:xymon-bounces at xymon.com> xymon-bounces at xymon.com] Namens Robert Herron
Verzonden: woensdag 30 augustus 2017 16:34
Aan: xymon Mailing List < <mailto:xymon at xymon.com> xymon at xymon.com>
Onderwerp: Re: [Xymon] Human readable disk space
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" < <mailto:user-6d8e227afca3@xymon.invalid> 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 < <mailto:user-af55987f6d56@xymon.invalid> 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 < <mailto:user-a2c231b1253e@xymon.invalid> 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
<mailto:Xymon at xymon.com> Xymon at xymon.com
<mailto:Xymon at xymon.com> Xymon at xymon.com
list Jeremy Laidman
Steffan The table shown in the disk test page is directly from the "df" command executed on the client. This can't be modified without also changing the parser (in xymond_client), because it assumes that the numbers are in blocks. It would be possible to make your own test column to use in place of "disk" and then reformat the client data message to your liking - perhaps even constructing an HTML table. However you'd either have to name it something other than "disk" and have two tests almost the same, or you'd need to somehow suppress the "disk" message from the xymond_client process. I'm not sure how you would do this. Of course it's open source, so you're free to adjust xymond_client to reformat the disk status message any way you see fit. In short, I don't see any easy way to do this. Cheers Jeremy
▸
On 30 August 2017 at 18:27, Steffan Noord <user-f8824a6d4da5@xymon.invalid> wrote:
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
list Jeremy Ruffer
That's the advantage of using df -B G. It's still working in blocks and just increases the size of the blocks. Jeremy Ruffer On 3 September 2017 at 10:48, Jeremy Laidman <user-71895fb2e44c@xymon.invalid>
▸
wrote:
Steffan The table shown in the disk test page is directly from the "df" command executed on the client. This can't be modified without also changing the parser (in xymond_client), because it assumes that the numbers are in blocks. It would be possible to make your own test column to use in place of "disk" and then reformat the client data message to your liking - perhaps even constructing an HTML table. However you'd either have to name it something other than "disk" and have two tests almost the same, or you'd need to somehow suppress the "disk" message from the xymond_client process. I'm not sure how you would do this. Of course it's open source, so you're free to adjust xymond_client to reformat the disk status message any way you see fit. In short, I don't see any easy way to do this. Cheers Jeremy On 30 August 2017 at 18:27, Steffan Noord <user-f8824a6d4da5@xymon.invalid> wrote: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
list Steffan Noord
Thanxs all Van: Xymon [mailto:xymon-bounces at xymon.com] Namens Jeremy Laidman Verzonden: zondag 3 september 2017 11:48 Aan: Steffan Noord <user-f8824a6d4da5@xymon.invalid> CC: xymon at xymon.com Onderwerp: Re: [Xymon] Human readable disk space Steffan The table shown in the disk test page is directly from the "df" command executed on the client. This can't be modified without also changing the parser (in xymond_client), because it assumes that the numbers are in blocks. It would be possible to make your own test column to use in place of "disk" and then reformat the client data message to your liking - perhaps even constructing an HTML table. However you'd either have to name it something other than "disk" and have two tests almost the same, or you'd need to somehow suppress the "disk" message from the xymond_client process. I'm not sure how you would do this. Of course it's open source, so you're free to adjust xymond_client to reformat the disk status message any way you see fit. In short, I don't see any easy way to do this. Cheers Jeremy On 30 August 2017 at 18:27, Steffan Noord <user-f8824a6d4da5@xymon.invalid <mailto:user-f8824a6d4da5@xymon.invalid> > wrote: 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