New features / wish list
Hi, it would be great if the following features could be added to one of the next releases :
1) Rule-based notificaton
Some devices can send e.g. syslog traps to OpManager. The trap OID is always the same, but the content may vary considerably. Some 'syslog-traps' are interesting, others not. It would be great if the uninteresting ones could be filtered out by e.g. message content (matching a string).
In the notification-profile, a filter could be implemented by adding a 'criteria option' check box similar to something like:
"select alarm variable" contains "string in a text box"
This option could then be checked together with e.g. "if trap is received from device".
2) Rule-based trap-receivers
Furthermore, it would be nice to change the message of a trap-receiver based on a certain string in the trap message.
In the trap-receiver window, this could be implemented by adding a button that allows adding/deleting multiple check boxes similar to something like:
if "select alarm variable" contains "string in a text box" then message = "text in a message box" and severity = "select severity"
3) Monitor devices by their importance
Currently, it is possible it is possible to set the polling interval for servers, desktops, printers, routers and switches (I'm waiting for firewalls). It would be interesting if - for each of these categories (especially for the server category) - the a importance level (High/Medium/Low) could be defined with a different polling interval. This would mean that the importance of each device has to be determined by the administrator. Critical devices ('high' importance) can then be monitored more frequently than others. This feature avoids setting the polling interval manually for critical servers.
4) Monitor services by their importance
Similarly to point 3), on a same server several services might be more important than others. The same 'importance concept' could be implemented for the services.
5) Allow read-only users to add comments
Read-only users can only clear and acknowledge alarms. It would be nice for other users to known why they cleared/acknowledge the alarm. Adding "Add comments" would solve this.
6) Launch mib-browser from device view
Instead of going to Admin/mib-browser and enter the device settings in this window, putting a shortcut in the device view window with all predefined settings (IP-address/name, community string) will facilitate the use of the mib-browser.
7) Sort the devices in each infrastructure view
Sorting the servers in the "details"-view by device-type (Linux, Windows,...), by name and by service would be very helpful to get a quick overview. This might also be applied to other device categories.
8) TNS ping for Oracle database
It would be nice if a Oracle TNSping could be added to the Application/Oracle monitors.
Regards,
Sacha
1) Rule-based notificaton
Some devices can send e.g. syslog traps to OpManager. The trap OID is always the same, but the content may vary considerably. Some 'syslog-traps' are interesting, others not. It would be great if the uninteresting ones could be filtered out by e.g. message content (matching a string).
In the notification-profile, a filter could be implemented by adding a 'criteria option' check box similar to something like:
"select alarm variable" contains "string in a text box"
This option could then be checked together with e.g. "if trap is received from device".
2) Rule-based trap-receivers
Furthermore, it would be nice to change the message of a trap-receiver based on a certain string in the trap message.
In the trap-receiver window, this could be implemented by adding a button that allows adding/deleting multiple check boxes similar to something like:
if "select alarm variable" contains "string in a text box" then message = "text in a message box" and severity = "select severity"
3) Monitor devices by their importance
Currently, it is possible it is possible to set the polling interval for servers, desktops, printers, routers and switches (I'm waiting for firewalls). It would be interesting if - for each of these categories (especially for the server category) - the a importance level (High/Medium/Low) could be defined with a different polling interval. This would mean that the importance of each device has to be determined by the administrator. Critical devices ('high' importance) can then be monitored more frequently than others. This feature avoids setting the polling interval manually for critical servers.
4) Monitor services by their importance
Similarly to point 3), on a same server several services might be more important than others. The same 'importance concept' could be implemented for the services.
5) Allow read-only users to add comments
Read-only users can only clear and acknowledge alarms. It would be nice for other users to known why they cleared/acknowledge the alarm. Adding "Add comments" would solve this.
6) Launch mib-browser from device view
Instead of going to Admin/mib-browser and enter the device settings in this window, putting a shortcut in the device view window with all predefined settings (IP-address/name, community string) will facilitate the use of the mib-browser.
7) Sort the devices in each infrastructure view
Sorting the servers in the "details"-view by device-type (Linux, Windows,...), by name and by service would be very helpful to get a quick overview. This might also be applied to other device categories.
8) TNS ping for Oracle database
It would be nice if a Oracle TNSping could be added to the Application/Oracle monitors.
Regards,
Sacha