|
|
| Intra-device dependencies | | 111 | |
Multiple-device dependencies | | 82 | |
Merging performance monitors with active monitors | | 82 | |
Web alarms : choice between the old (2006) and the new (V11) behaviour | | 33 | |
Device states : Normal / Warning / Critical instead of Up / Down | | 130 | |
Ability to control how individual device state is reflected in group state | | 68 | |
Ability to configure specific monitors so that they don't trigger device-level actions | | 101 |
|
| | | |
| | | Supreme Being
Group: Forum Members
Last Login: 9/25/2008 3:02:37 AM
Posts: 87, Visits: 154 |
| | Hello, what is really really really frustrating is the short timeout of 60 seconds on active monitors.
I have scripts that sometimes just run for two or more minutes, depending how busy the polled device is. I am currently living with the fact that I have approx. 20 -30 fail alarms a day.
Annoying! Also, the format of the re-occuring reports needs to be customizable and brushed up in general, they are seriously un-professional! Regards,
Andi |
| |
| | | Forum Member
Group: Forum Members
Last Login: 7/11/2008 9:43:24 AM
Posts: 33, Visits: 53 |
| | Following on from Andi's comment, Active script monitors should always respect the default return value. If I have Context.SetResult 0, "Check could not be performed!" ' Set the default return value as success to avoid false alarms
as the first line of my active script, then if the script times out the monitor should NOT report as being down. For example, if I'm checking for the existance of a file on a server using an active script I don't want the monitor to report as down if the script times out for some reason if I've set the default return value as 0. I only want to report the monitor down if the test has completed. If I wanted the monitor to report a failure in the event of the script timing out the I would set the default return value as 1 with Context.SetResult 1, "Check could not be performed!" The current situation significantly weakens the active script feature which must already be overused because things like performance monitors cannot be directly used to trigger alerts. Just my two cents worth.... |
| |
| | | 
Time Traveler
Group: Forum Members
Last Login: Today @ 1:04:23 AM
Posts: 349, Visits: 5,722 |
| Sergio (3/19/2008)
MB-NS is right I think. We tried to focus on features that you really can't "work around". Most of them are really core features we would like to see in the engine.I would also like to get more detailed information about which objects are available for active scripting in Active/Performance Monitor Scripts. For example: you can use the "WbemScripting.SWbemLocator" object in Active Monitors, but not in Performance Monitors. There is NO information from Ipswitch about this issue... New "feature": a better scripting documentation. Regards, LLS71
---
Leonardo Schieder
A. PORR AG - http://www.porr.at
System Managementhttp://www.xing.com/go/invita/7686498 |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 7/17/2008 2:00:47 AM
Posts: 7, Visits: 15 |
| | |
| | | Forum Newbie
Group: Forum Members
Last Login: 4/8/2008 3:10:06 AM
Posts: 2, Visits: 7 |
| | |
| | | Supreme Being
Group: Forum Members
Last Login: 7/2/2008 7:03:13 AM
Posts: 95, Visits: 237 |
| | Hello All At first I'd like to thank Sergio for creating this topic. You know It's a pity that I can't choose all 7 features. And second I'd like to make 3 wishes to IPSwitch programmers. All about ActiveScript 1. Add an "Exit"(maybe - return()) function to the script syntax. In the script body I make some calculation and then I wannt to set result and finish scripting flow, for example I explore that this device haven't SNMP access - therefore I need to set result "error" and go out of the script, now I can't do this. This problem has "work around", unlike next 2 problems 2. Please make access to Active Monitor arguments ("Argument","Comment" fields) from Active Monitor Script 3. Please solve this problem: When I make 2 different devices with the same IP address(not link!) and if I use this Active Script code: var nDeviceID=Context.GetProperty("DeviceID") I get the same device ID in both case. The thing is - WuG figure that IP address is unique but not DeviceID As a result - I don't really sure that I work with necessary device in my Active Monitor Script 2,3 points I report to Daniel Donnely but he can't help me...
Juriy Gordubal |
| |
| | | Time Traveler
Group: Forum Members
Last Login: Yesterday @ 10:25:48 AM
Posts: 534, Visits: 1,880 |
| Juriy (3/31/2008)
1. Add an "Exit"(maybe - return()) function to the script syntax.In the script body I make some calculation and then I wannt to set result andfinish scripting flow, for example Iexplore that this device haven't SNMP access - therefore I need to set result"error" andgo out of the script, now I can't do this. This problem has "work around", unlike next 2 problems
Well, can't you just use If Then Else to do that ? Unless I misunderstood something.
Juriy (3/31/2008)
2. Please make access to Active Monitor arguments ("Argument","Comment" fields) from Active Monitor Script
This can be done using a SQL query.
Juriy (3/31/2008)
3. Please solve this problem:
You're right, there is no way around this, but if intra-device dependencies were implemented we wouldn't need 2 devices with the same IP address anymore. |
| |
| | | | |
|