We are new to Kaseya and we are trying to create monitor sets for low disk space. However, we would like to have the following conditions.
Create 1 alarm only and send the an email if disk space is lower that 10% (This alarm/email shouldn't repeat itself)
Create 1 alarm only and send the an email if disk space is lower that 5% (This alarm/email shouldn't repeat itself)
Create 1 alarm only and send the an email if disk space is lower that 3% (This alarm/email should repeat itself every 6 hours)
We tried leaving the re-arm alarm option blank thinking that would prevent the alarm from generating itself multiple times however it just keeps sending alerts and creating alarms which end up filling the Alarm logs and doesn't make then really useful.
Any suggestions will be really appreciated!
We developed "Smart Monitors" for this type of situation.The chief consideration for this effort is that percentages represent different amounts depending on the volume size - 10% of a 100G drive is a reasonable alert threshold, while 10% of a 2TB volume usually isn't.
Our smart monitors are apps that we wrote - they are deployed and then monitored by Kaseya, but the app does the work. The Disk smart monitor does the following:
After 6 months of dedicated research into the Kaseya alerting/monitoring methods, we chose to develop custom monitors that Kaseya could track rather than struggle with the configuration options that Kaseya provides.This isn't a Kaseya-specific issue, as some of the largest and most expensive monitoring systems (such as IBM Tivoli and HP OpenView) work similarly when it comes to disk monitoring.
Smart Monitors can be customized to alert once or once every n days or even perform local actions. When monitored on a workstation, for example, a pop-up can display a warning to the user and suggest cleaning up or archiving old documents.
We currently have 5 classes of Smart Monitors that handle Disk Capacity, AV Status, Safe Mode Detection, Time Sync Validation, and Internet Connection Failover detection. There are a few more somewhere between the "drawing board" and development stage. You can get more info about these on Kasey's Automation Exchange or our web site.
Bottom line - you might be better served by thinking outside the Kaseya Monitor box for something this specific.
As an alternative to Glenn's excellent post, you could put a very long re-arm period that would be very difficult to re-arm:
Glenn & Nicolas,
Thank you both for the replies!
We will start looking into Glenn's suggestion but in the mean we have set up the monitor sets as Nicolas suggested.
Another quick question, we have set the alarm to re-arm itselft in 365 days. However, let's say we cleared enough space so that it doesn't even meet the collection treshhold. If the drive gets full again will Kaseya start collecting data again and rearming the alarm before the 365 days given that it started a new collection of data?