Event Log Overview

During the installation and configuration of the N1 System Manager, you can configure which events to log and you can also interactively configure severity levels for event topics. See Configuring the N1 System Manager in Sun N1 System Manager 1.3 Installation and Configuration Guide.

Even if a log is not saved, it can still generate an event notification.

Use the show log command to view the following information about events:

• Date – The date and time of the event.

• Subject – The server on which the event occurred.

• Topic – The topic of the event, which can be useful for setting up event notifications. Refer to Setting Up Event Notifications for information.

• Severity – Relative severity of the event.

• Level – Relative level of the event.

• Source – The name of the component that generated the event. For events that are generated during the execution of a job, the source is the job number.

• Role – Role or user name of the user who initiated the event.

• Message – Complete text of the event log message.

The n1smconfig script can be used to change the number of days for which event logs are kept. Reducing the number of days for which event logs are stored reduces the average size of the event log files. This task ensures that the event log file size does not impair performance. The n1smconfig script is stored at /usr/bin for both the Linux and Solaris OS platforms. This script can be used to set the number of days for which event logs are held. To configure event logging, specify an event category and a resource category. The following event categories are defined:

• Action

• Ereport

• Lifecycle

• List

• Problem

• Statistic

• all

Use the all event category to indicate that all events are to be logged. To understand how other event categories relate to actual events, see the event notification topics at create notification in Sun N1 System Manager 1.3 Command Line Reference Manual. General log files are saved to the syslog file at /var/adm/messages or /var/log/messages