Administration Guide › Subscription › Self-Monitoring Events for Subscription › Monitor Subscription Events

Monitor Subscription Events

You can monitor the successes and failures of the subscription update processes by viewing self-monitoring events for subscription.

To monitor subscription processing events

1. Click the Administration tab and the Services subtab.
2. Click Subscription Module in the Service List.
3. Click the Self Monitoring Events tab for either the Subscription Module or for a host listed under Subscription Module.
4. Review the displayed event details.

   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.

   • CA Severity

     The severity of the event, where

     • Unknown - Unknown events, events not mapped to CEG, or unclassified events
     • Information - General system operations information, security related information, or a notice
     • Warning - Unusual changes, a normal but significant condition, failed operations, or degraded performance
     • Minor Impact - Minor impact to a system, a function, or security
     • Major Impact - Major impact to a system, a function, or security
     • Critical - Immediate action is required; there is a likely security breach.
   • Date

     When the event occurred.

   • Receiver

     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.

   • Receiver Host

     The host name of the CA Enterprise Log Manager server that is the Receiver.

   • Category

     The category of the event. Configuration Management is the event_category for subscription module events.

   • User

     The username or identity that initiated the action expressed in the event information. This is the source_username field in CEG.

   • Action

     The action that caused the event to be generated. This is the event_action field in CEG.

   • Result

     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.

   • Result Description

     The message text. If the Result column displays Failure, view the Result Description text.

5. View details in the Event Viewer. Here you can view changes such as those made to a configuration value such as update start time.