You can monitor the successes and failures of the subscription update processes by viewing self-monitoring events for subscription.
To monitor subscription processing events
Some of the fields displayed for self monitoring events reflect the CEG standard way of referring to common actions across vendors. The Ideal Model is based on this hierarchy: event_category, event_class (within the category), event_action (within the class), event_result, and event_severity. The CA Severity shown in this report is the CA interpretation of the severity.
The severity of the event, where
When the event occurred.
The component that failed to successfully complete the current process. This could be either a subscription proxy or a subscription client. If it is a subscription proxy, it could be the default proxy, an online proxy, or an offline proxy.
The host name of the CA Enterprise Log Manager server that is the Receiver.
The category of the event. Configuration Management is the event_category for subscription service events.
The username or identity that initiated the action expressed in the event information. This is the source_username field in CEG.
The action that caused the event to be generated. This is the event_action field in CEG.
S for Success; F for Failure. The result of the event action is the event_result field in CEG. Other actions are Accept, Reject, Drop, and Unknown.
The message text. If the Result column displays Failure, view the Result Description text.
Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |