Tullibo.com
Systems & Process Improvement: some must read resources→
←Massive MSP opportunity – Mac Support

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?

Related posts:

  1. A smarter way to handle Kaseya Low Disk Space Alerts for PCs It still amazes me the volume and number of...
  2. Editing Kaseya “INDividualized” & Standard Monitoring sets made by another admin Ever had to edit another admin’s IND monsets on...

Related posts brought to you by Yet Another Related Posts Plugin.

Bookmark and Share

Facebook Twitter StumbleUpon del.icio.us Digg Reddit Technorati RSS

Posted on 1 March 2010

  • What did you enter for warning %, Trend Activated, Trending Window, Re-Arm Trending and any other setting?
  • tullibo
    Hi marc

    I tend not to use the trending features and instead look at weekly report of disk usage across all servers on one single report. IMO much less time consuming than dealing with individual trending alerts. I figure if you're going to use trending to alert then you my as well just alert.

    My rearm time on servers is usually 24 hours for alerts.
  • @michaelbgray - disagree entirely with using snmp to monitor disk space...in my mind, if you need to stack two systems on top of each other to get one system working then the first system simply isnt working properly!

    K disk monitoring definitely has its foibles and shortcomings but between using the inbuilt disk alerts and monsets and if you really need a third fallback, event log monitoring for low disk alerts, I think all bases are covered. The weakness would probably more lie in getting a helpdesker or NOC staffer to respond quickly enough to the low disk alert that it does not become so critical as to cause a real server problem.

    I haven't played extensively with snmp in K2 but I still think snmp in kaseya has a long way to go, granted something is better than nothing though
  • michaelbgray
    We dont use disk space monitoring for servers in Kaseya because of the reasons you mention above. If I were going to do it, I'd probably poll it with SNMP. Have you given that a shot?
blog comments powered by Disqus