Parents-in-law hosting a party in my house and I have toddler duty -perfect beta testing time
The two items I took for a spin on b4 include the Device Studio and Alert Manager while logged in as default admin account:
Device Studio:
- I am getting more comfortable with the interface but it's like getting a new car - no doubt better but just gonna take some time to find where everything is now
- Stuck in a loop where I created a new Poller, scanned nodes and it didn't match anything, went back to change a data source that works on the test node, but on assigning it either is not rescanning or seems to think even the test node does not meet the criteria. Duplicate and edit then rescan has the same results so it would seem I can't figure out why a test node that works doesn't get assigned?
- Going back to edit an existing poller should allow you to edit just one tab and finish rather then walk through all steps again.
- I would prefer Poller Name Package above tags - I keep putting the name as the tags but then I might just be thick.
- The specify data source section should include a column (even if mouse over) that shows OID selected.
- Import Poller not working - Error on Page (IE 8) which seems to be JScript error. Export working as expected.
- The Pick OID window is throwing up non-HTTPS warnings for me
- The Data Source modal window seems to have some variable-text spacing issues - see screen shot below where it seems like the polled value is "30a" and "Orion expects Numbervalue in bytesfor Used Memory."
- Enable/Disable scanning on adding new nodes should provide a list of ALL enabled during adding new nodes
- When adding a new node (HP server) under CPU & Memory it preselected Fortimanager by Solarwinds instead of default cpu & memory -assigned Fortimanager after adding.
- While I enabled scanning for several other pollers those did not show up next to Fortimanager above - even if they did that list is gonna grow too long - please consider moving to UnDP tab or new discovery step?
- Encouraged to see UCS 6100 FI listed but my 6296 worked out of the box with the native CPU & Memory - not sure the 6100 requires a different poller but they are End Of Life (sales).
- I have only one machine type that doesn't work with the native pollers and that doesn't even have OID's so it's never gonna work - when can I use this for more technologies and for Hardware Health stats?
Alert Manager:
- VERY dismayed not to see variable or SQL query on the email Trigger Action (providing variables or SQL here is the best way to provide meaningful alert emails)
- I would have expected to be able to choose from existing Alert Actions (listed in Alert Manager) for a new Trigger Action - I assume this means we don't get one action to many alerts :-(
- When creating Trigger action the Simple Condition Builder seems to not yet wired - simple condition first drop down (shown below) is empty list and clearing condition sends me back to Advanced Condition Builder
- No ability to see the results of your Trigger Condition :-(
- Editing existing alert requires sequencing through entire menu set - should allow finish at any step if the prerequisites are already satisfied
- I don't understand the wording for "Evaluate whether trigger condition of this alert met every [60] [seconds] and prefer the previous version "Check this alert every [1] [minute]
- I assume that the scheduling function is yet to be wired in as the radio button was greyed out.
- Did not test import/export from itself or from existing win32 alert trigger actions
- Unable to use the Test action modal as it is not providing any objects. Test Action button on Action Manager tab does not even open a window.
Happy to see:
- Interface type (Access/Trunk) and Vlan Name
- Reports and alerts based on vlan information (i.e., alert if interface is assigned vlan 1 AND not shutdown)
- Ability to choose which custom properties to show on custom properties resource
- Saving the best for last - the ability to add search variables into custom query "SWQL" resource (this fundamentally changes my plans so I might not expand as much internal report writer or external SQL Reporting Service user reports.
