≡ Menu

Performing Notifications and Escalations with Netcool/Impact

in Best Practices, IBM, Implementation, IT Process Automation, Netcool/Impact, OPAL, Tivoli, Usability, Value

Our fifth Netcool/Impact OPAL contribution!

Available here.

-snip-

Netcool/Impact can send notifications via email, instant messages, and paging (email based or CLI based). Netcool/Impact provides an effective way of notifying people about events occurring in your environment. The event can exist in Netcool/OMNIbus, other SQL based data sources, on a JMS bus, or it can sent via Web Services message. Impact can trigger a notification policy to run on receipt of an event in any of these sources. The notification policy can send a notification to a recipient identified in the event or it can find the recipient in an external data source.

Impact can also receive emails and instant messages. When a message is received, Impact can run a policy which parses the message and takes some action. A good example of using this functionality would be to have someone acknowledge receipt of a notification by forwarding the email to Impact, with the word acknowledged in the message body. Impact could parse that from the message and flag the event. In the same scenario, if the recipient has not acknowledged the notification within a specified time period, the event could be escalated by sending a notification to a backup contact, or the original contact supervisor.

Impact allows for a great deal of logic to be applied to notification scenarios. You can control who gets a notification, when they get it, how the message appears, what information is in the message, how to escalate, etc. Information related to the event that resides in other sources can be included in the message, saving the recipient a great deal of time. For example, providing a support phone number in a notification of a software issue could be of great benefit to someone in their car, on a train, or at lunch, without access to this information.

Comments on this entry are closed.