Comments
-
I've tried in Chrome and IE on two different PCs, and get the same thing. I am able to access my LEM console with no problems through both browsers.
-
I've removed the disk type condition and the rule still does not trigger, per the above comments. The disk type is not the problem here, I have other alerts that use the exact same disk type condition and they work with no problem.
-
Absolutely! They've scheduled a call with me Tuesday morning with their Development to take a look at it. Thanks aLTeReGo for getting this pushed through so quickly!!
-
Ok, I was searching for the exact error I was seeing, so those didn't come up in my search results. Thanks again for the help!
-
I decided to go with the "right" option and open a support ticket: 791492
-
Son of a........ That's what I get trying to do calculations myself instead of letting a computer do them, huh? I think in my head, I did "bytes -> megabytes -> gigabytes". So, I officially declare that kilobytes no longer exist, I have broken the metric system. Let it be known. I do feel like an idiot now, though... THANK…
-
Still does not trigger
-
Looks like the Remote Registry service restart fixed it. Thanks! Also, did I miss this in a KB article? I found one saying to restart the WMI service, but didn't see anything about the remote registry service.
-
I tried that, and it does show the correct disk (only one right now, since I'm still testing this alert/custom property). If I place the trigger condition into the scope section as well, it still shows this disk, but once I move it to the trigger condition, it does not trigger.
-
I do not want alerts based on percentages. That is the whole point of creating the custom properties, to be able to adjust the threshold individually per volume, by size instead of percentage. If I wanted to use percentage, I could just use the global variables that are already in place and override them.
-
It does have a space in it. I deleted the value, started typing the F and had a choice of both "FixedDisk" and "Fixed Disk". I checked the drive itself and the type value does have a space in it. I also checked other disk alerts that are working, based off more static thresholds, and those have a space in them as well.
-
Anywhere from 2 months to 2 weeks ago
-
For this one, it's a combination of Exchange 2000-2003 template and Windows Server 2003-2012 Services and Counters template. I'll try restarting the remote registry, but if I can view the counters with no problems through perfmon and WMI remotely, would rebuilding them do any good for that?
-
I know I can use the rules and actions, I've already got that part set up. What I'm asking about is pulling certain info out of the trap to put into the email alert. For example, if my trap is 11/18/2014 2:19 PM : StorageManagement-MIB:storageManagementEvent.0.904 SNMP Trap Received Time:11/18/2014 2:19:07 PM…
-
I know this is an older thread now, but just wanted to let everyone know that I did receive another update from support: I just wanted to drop you a line to let you know that development has confirmed that this is going to be resolved in the 6.3 release. Unfortunately, I do not have a time frame to give you for the release…
-
Just got an update to this, it has been flagged as a bug and they are looking into a fix: This is a bug in the product. The problem is that where we display the old db name we are using the database identity. This databse identity is not something that is changed with the database renaming. Thus, even if you remove the…