Overview of Events

Management & Control Services (MCS) records and logs any system events that are generated either by MCS itself, or by any MCS-managed product. Each MCS-managed product can log its own events in the MCS event log; the types of events that a product can log are specified by that product.

Using MCS, you can specify which events you want to log, the maximum number of log files to save, and the maximum size of each log file. You can also manage log files by closing log files, opening new log files, and deleting old log files as needed. For instructions on managing MCS event logging, see Managing Events.

Understanding Events vs. Tracing

MCS provides both event logging and trace logging services, which record the same types of events. However, you can use each service for different purposes:

• Events, which are continually logged by MCS and MCS-managed products, can be used to store and monitor a running log of events that occur within your system. The event service can generally run unattended, while allowing you to view events as needed.

• Tracing, by contrast, is not enabled by default for either MCS or MCS-managed products. You can create custom trace configurations as needed to help track and troubleshoot any problems that occur. Traces can be limited to a particular product (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.

	Managing Events
	Viewing Events
	Overview of Tracing