When creating a custom field is the value in bytes or gigs or ?

krfitzgerald

I created a custom field for my volumes and made it an integer type. I assumed the value was in bytes because that's what it was when I tried to do my disk space alerts in a regular simple condition in alert manager. When I tried to add the value for 30 gig in bytes into the integer field it was too long to fit so it threw an error message. I deleted the field and readded it as a text. So am I right in assuming that the value will be in bytes or is it in gig?

smargh

The value is just an integer, with a maximum value equivalent to around 2 gigabytes when converted to bytes. This makes it unsuitable for directly comparing available & used space, because they are in the database as bytes only.

I use custom fields to store limits for megabytes. Then, use a custom SQL volume alert but divide the value in the database by 1024, then 1024 again for megabytes.

For example, this is what I use. My custom field is called "Minimum_Free_MB", and I'm sure it can be optimised a little:

WHERE  (  (Volumes.Minimum_Free_MB IS NOT NULL)  AND   (Nodes.Vendor = 'Windows')  AND   (Volumes.Caption LIKE '%:\%')  AND   (   (Volumes.VolumeType = 'Fixed Disk')   OR    (Volumes.VolumeType = 'Unknown')  )  AND   (NullIf(VolumeSize,-2)-NullIf(VolumeSpaceUsed,-2))/1024/1024 < Volumes.Minimum_Free_MB)  AND   (Volumes.VolumeSize >= 1))