I've been curious about making a monitor set for disk space, however i am rather new to Kaseya and have no idea how to go about it. I'm using Kaseya 2008, obvious i know but i still thought id state it!
<?xml version="1.0" encoding="ISO-8859-1" ?>
-<MonitorSet name="Disk Free Space" description='Dynamically count all drives and alarm if any drive goes below 1000MB.'>
<Counter name='Drive' description='null' counterObject='LogicalDisk' counter='Free Megabytes' counterInstance='*ALL' counterSampleInterval='300' collectionOperator='Over' collectionThreshold='-1' trendTimeSpan='1209600' trendReArm='3600' thresholdOperator='Under' thresholdAmount='1000' thresholdDuration='25' thresholdWarning='10' thresholdReArm='3600'/>
JpinkstonWe have that issue with sets now. We are not on K2. The only answer we have gotten from Kaseya is to remove the sets, let all the counters delete, and then reapply.
This works, but obviously is not a solution. Can you try that on your test box and let us know how it goes? We will definitely hold out on the upgrade if this issue is present. All of our monitoring sets for disk space use the *ALL.
CCDaveI tried this already and had no luck. However, I think I did find a little insight into how the *ALL actually works.
In the Monitor Lists section you can add your own Counter Instances. The *ALL simply adds all Counter Instances already defined in Kaseya (by Kaseya or yourself) to the list. In K2008 it then seems to filter out anything that doesn't match. In K2 it doesn't. That appears to be the problem.
I've opened a ticket... wish me luck!
kcearsHave you gotten any responses on this issue? I'm seeing the same thing, but with using *ALL for Services, not Counter Instances. However that never worked in K2008, but it did work in either RC1 or 2, but now doesn't work right in the final release, even though multiple people at Kaseya told me it would be working correctly in K2. I started a ticket but haven't heard anything back other than "it's been escalated".