Overview: Events and Tracing

Management & Control Services (MCS) can record and log system events and trace data generated either by MCS itself, or by any MCS-managed product or component in which event or trace logging is supported.

Logging Events

Events can be used to store and monitor a running log of events that occur within your system. The event service can typically run unattended, while allowing you to view events as needed. Event logging is enabled by default in EXTRA! X-treme and can also be used by the following MCS services:

Each MCS-managed product or service can log its own events in the MCS event log; the types of events that can be logged are specified by the product. For instructions on managing MCS event logging, see Managing Events.

Logging Trace Information

In contrast to event logging, you create custom trace configurations only as needed to help track and troubleshoot any problems that occur. Although it is not enabled by default, you can use trace logging with Terminal Viewers. (To enable tracing, you must configure and then start the configured trace.) Terminal Viewers specifies the type of information that can be traced, and creates a separate trace file for each host session.

Trace can be used with both terminal and printer configurations. Trace entries are logged locally, and reported to MCS only when requested. Using MCS, you can view and save trace data in one central location.

Traces can be limited to a particular component, or they can be configured to follow a task across a series of clusters or servers. When you are finished with a particular trace, you can stop or even delete a trace configuration, preventing the tracing service from consuming unnecessary resources and disk space.

Tracing Across Components

MCS provides two types of tracing: component and end-to-end. The trace style is specified when a new trace is configured, and can be updated later for an existing trace.

Component tracing applies to only one component of an MCS-managed product. All activity for the specified component is traced and recorded for that component only, on a single computer or cluster.

End-to-end tracing provides a method for tracing a particular task across several components, which may be installed on one or more computers or clusters. All of these components may be installed on a single server or cluster, or they may be spread across multiple individual servers.

MCS uses correlation IDs when it records trace files. For component-style traces, the correlation ID uniquely identifies each trace. For end-to-end trace files, the correlation ID is passed along with the task from one component to the next, and is used by MCS to correlate and display all of the related trace entries at the MCS console when requested. Each correlation ID also includes an index number, which is incremented by one at each stage of the task's progress. For component-style traces, the index number is always 1.

Related Topics
Bullet Monitoring Client Activity, Overview
Bullet Managing Events
Bullet Viewing Events
Bullet Enabling Tracing in Terminal Viewers
Bullet Configuring a New Trace
Bullet Starting or Stopping a Trace
Bullet Viewing Traces