Often a single event coming across the Event Console is not important unless seen in context with other events. By constructing a series of message records and actions, you can be notified and take action if two or more events occur that together have more significance to your enterprise than any one of the events may have when it occurs in isolation.
For example, assume you have two PCs in your accounting department. If one goes down, it is a problem and you probably have established policies to deal with such an occurrence. However, should the second also go down, the problem suddenly becomes critical. The action you want to take in this situation may be quite different.
A solution is to define message records to trap events coming to the Event Console informing you that Accounting PC #1 and Accounting PC #2 are coming down. Then, for each message record, define message actions that test for the occurrence of the other event. As a result, you will be automatically notified of the critical situation that exists in the Accounting department.
|
Copyright © 2010 CA.
All rights reserved.
|
|