Hi Team,
I am trying to set the disk space alerts based on GB instead of % since the disk size is large.
So I set critical alert at free space less than 200 GB. The drive size is 14 TB. I used the below command in the argument.
-t 'xxxxxxxx' -P 5693 -M 'disk/logical/M:|/free' -w 250 -c 200: -u G
When I run it to see the result I get this
OK: Free was 2116.22 GB | 'free'=2116.22GB;250:;200:;
But the actual free size on the drive is 1.92 TB = 1966 GB. So there is a difference of 160 GB.
When I changed GB to MB in the command the difference was down to 100 GB.
So is it because of conversion ? Still looks like a huge difference when setting up the alerts. Do you guys have any advise?
Disk space alert based on GB
Disk space alert based on GB
Last edited by ssax on Thu May 06, 2021 4:56 pm, edited 1 time in total.
Reason: Removed token from command
Reason: Removed token from command
Re: Disk space alert based on GB
What does this one show?
Code: Select all
-t 'xxxxxxxx' -P 5693 -M 'disk/logical/M:|/free' -w 250 -c 200: -u GiRe: Disk space alert based on GB
Tried what you shared. -t '***********' -P 5693 -M 'disk/logical/C:|/free' -w 250: -c 200: -u Gi
It gave a weird result. For the same server it is now showing only 30 GB free whereas the free space is 1.2 TB.
CRITICAL: Free was 30.27 GiB | 'free'=30.27GiB;250:;200:;
It gave a weird result. For the same server it is now showing only 30 GB free whereas the free space is 1.2 TB.
CRITICAL: Free was 30.27 GiB | 'free'=30.27GiB;250:;200:;
Re: Disk space alert based on GB
Your original post was using M: but the one you just sent is showing C:, could that be related?
Re: Disk space alert based on GB
Sorry, my bad.
Yup, looks like using Gi gives a close result. This should solve the issue. Thanks.
Yup, looks like using Gi gives a close result. This should solve the issue. Thanks.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Disk space alert based on GB
Locking threadsahilrana wrote:Sorry, my bad.
Yup, looks like using Gi gives a close result. This should solve the issue. Thanks.