Issues with and Suggestions for OpManager 5.5
I have noticed several issues with OpManager 5.5, some of which have probably already been noted. Here goes:
PROBLEMS
1. After configuring SNMP community, it remains at "public" when adding devices
2. I cannot make WMI monitoring work at all. I remove the SNMP monitors and add the WMI monitors with no problems. The monitors say they are running fine, but no graphs are ever created and the cpu/memory/disk section simply says "no data available. If I remove the WMI monitors, re-add the SNMP monitors and do a re-discover, the graphs start working again.
3. Windows Event Log monitoring appears to only work on the machine I have OpManager installed on. I have all 2003 servers (including the one running OpManager) set to monitor for all application and system log failures. I have the same notification profile assigned to all the servers. When an error or warning event occurs on the machine OpManager is running on, I get an e-mail and it shows up in the main "dashboard" screen. For my other servers, nothing is trapped.
REQUESTS
1. When adding a device, user should be able to specify SNMP and/or WMI for use by monitoring agents. Presently, you can only add a device by filling out SNMP information. There should be entries for Windows username/password here and perhaps check boxes for enabling/disabling WMI/SNMP.
2. It would be nice to have a "traffic" tab on the main screen where you could have a one-stop page for viewing traffic. This page should be configurable, as to which traffic graphs to display. I think of MRTG, where you can have a single index page with all your graphs. Say you have 4 important interfaces, perhaps spread out among 4 different devices. The traffic page could be set up to show traffic graphs for those 4 interfaces.
3. A text file monitor, where you could configure text files to monitor and notify you on change, perhaps on matching words, etc.
New to ADSelfService Plus?