SYSLOG Alert Message Format
If an alert is configured with the Send Syslog Message action, it will produce a syslog
message payload containing localized text consisting of the following standard fields. Each
field will be prefixed with the field name in CAPITAL letters followed by a colon and
whitespace character.
Table 101 SYSLOG Alert Message Formats
|
|
|
SUNW-MSG-ID
|
The stable Sun Fault Message Identifier associated with the alert. Each system
condition and fault diagnosis that produces an administrator alert is assigned a
persistent, unique identifier in Sun's Fault Message catalog. These identifiers can
be easily read over the phone or scribbled down in your notebook, and link to a
corresponding knowledge article found at My Oracle Support (https://support.oracle.com/) "Predictive Self-Healing" (Doc ID
1154428.1). |
|
TYPE
|
The type of condition. This will be one of the labels: Fault, indicating a
hardware component or connector failure; Defect indicating a software defect or
misconfiguration; Alert, indicating a condition not associated with a fault or
defect, such as the completion of a backup activity or remote replication.
|
|
VER
|
The version of this encoding format itself. This description corresponds to
version "1" of the SUNW-MSG-ID format. If a "1" is present in the VER field, parsing
code may assume that all of the subsequent fields will be present. Parsing code
should be written to handle or ignore additional fields if a decimal integer greater
than one is specified.
|
|
SEVERITY
|
The severity of the condition associated with the problem that triggered the
alert. The list of severities is shown below.
|
|
EVENT-TIME
|
The time corresponding to this event. The time will be in the form "Day Mon DD
HH:MM:SS YYYY" in UTC. For example: Fri Aug 14 21:34:22 2009.
|
|
PLATFORM
|
The platform identifier for the appliance. This field is for Oracle Service use
only.
|
|
CSN
|
The chassis serial number of the appliance.
|
|
HOSTNAME
|
The canonical name of the appliance as defined by the System Identity
configuration. See System
Identity. |
|
SOURCE
|
The subsystem within the appliance software that emitted the event. This field
is for Oracle Service use only.
|
|
REV
|
The internal revision of the subsystem. This field is for Oracle Service use
only.
|
|
EVENT-ID
|
The Universally Unique Identifier (UUID) associated with this event. Oracle's
Fault Management system associates a UUID with each alert and fault diagnosis such
that administrators can gather and correlated multiple messages associated with a
single condition, and detect duplicate messages. Oracle Service personnel can use
the EVENT-ID to retrieve additional postmortem information associated with the
problem that may help Oracle respond to the issue.
|
|
DESC
|
Description of the condition associated with the event.
|
|
AUTO-RESPONSE
|
The automated response to the problem, if any, by the Fault Management software
included in the system. Automated responses include capabilities such as proactively
offlining faulty disks, DRAM memory chips, and processor cores.
|
|
REC-ACTION
|
The recommended service action. This will include a brief summary of the
recommended action, but administrators should consult the knowledge article and this
documentation for information on the complete repair procedure.
|
|
The SEVERITY field will be set to one of the following values:
Table 102 SYSLOG Severity Fields
|
|
|
|
Minor
|
LOG_WARNING
|
A condition occurred that does not currently impair service, but the condition
needs to be corrected before it becomes more severe.
|
|
Major
|
LOG_ERR
|
A condition occurred that does impair service but not seriously.
|
|
Critical
|
LOG_CRIT
|
A condition occurred that seriously impairs service and requires immediate
correction.
|
|