Server disk space monitoring with Kaseya

Written by BT

Topics: Kaseya

kaseya-disk-spaceI’ve seen MSPs burn hours applying customized monsets to monitor server disk drive space for different drive letters. Here’s how I do it, simple and effective:
1-I use the in-built disk space alert and set this to alert at 3% free
I find 3% gives me the right balance to capture low disk alerts for both big and small disks.
Unfortunately, this alert only works after a latest audit is done on a server. I like to schedule my server latest audits nightly, but still, a nightly check of disk space is hardly realtime monitoring.
My main motivation behind using the inbuilt monitoring for disk space is to capture instances where no monset has been applied for disk space monitoring or the monset has stopped capturing data for whatever reason.
2-I use a single disk space monset that monitors free disk space on all drives.
I have a single monset that monitors all disk drive instances for both % free and GB free.
Again here, I trigger an alert at 3% disk space free or less and also at 2.5GB free or less. Again using a combination of % free and GB free gives me a good balance for coverage of a variety of disk drive sizes.
Not that here I use the *ALL instance which allows the set to monitor for all disk drive instances. Once the set is applied to servers Kaseya seems to do weird things and modify the monset itself and add drive letters to the monset. This will cause the monset to attempt to capture data for drives that do not exist but I figure no harm done, I rather that than not monitoring drives at all because a tech missed a monset.

I’ve seen MSPs burn hours applying customized monsets to monitor server disk drive space for different drive letters. Here’s how I do it, simple and effective:

1. I use the in-built disk space alert and set this to alert at 3% free

I find 3% gives me the right balance to capture low disk alerts for both big and small disks.

Unfortunately, this alert only works after a latest audit is done on a server. I like to schedule my server latest audits nightly, but still, a nightly check of disk space is hardly realtime monitoring.

My main motivation behind using the inbuilt monitoring for disk space is to capture instances where no monset has been applied for disk space monitoring or the monset has stopped capturing data for whatever reason.

2. I use a single disk space monset that monitors free disk space on all drives.

I have a single monset that monitors all disk drive instances for both % free and GB free.

Again here, I trigger an alert at 3% disk space free or less and also at 2.5GB free or less. Once more, using a combination of % free and GB free gives me a good balance for coverage of a variety of disk drive sizes.

Not that here I use the *ALL instance which allows the set to monitor for all disk drive instances. Once the set is applied to servers Kaseya seems to do weird things and modify the monset itself and add drive letters to the monset. This will cause the monset to attempt to capture data for drives that do not exist but I figure no harm done, I rather that than not monitoring drives at all because a tech missed a monset.

kaseya-disk-space

What’s your feedback? Any other ways you’re monitoring disk space?