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 white (negative) space character.
Table 3-56 SYSLOG Alert Message Formats
Field Name | Description |
---|---|
|
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). |
|
The type of condition. This will be one of the labels: |
|
The version of this encoding format itself. This description corresponds to version "1" of the |
|
The severity of the condition associated with the problem that triggered the alert. The list of severities is shown in the next table. |
|
The time corresponding to this event. The time will be in the form |
|
The platform identifier for the appliance. This field is for Oracle Service use only. |
|
The chassis serial number of the appliance. |
|
The canonical name of the appliance as defined by the System Identity configuration. See System Identity. |
|
The subsystem within the appliance software that emitted the event. This field is for Oracle Service use only. |
|
The internal revision of the subsystem. This field is for Oracle Service use only. |
|
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. |
|
Description of the condition associated with the event. |
|
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. |
|
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 3-57 SYSLOG Severity Fields
Severity | Syslog Level | Description |
---|---|---|
Minor |
|
A condition occurred that does not currently impair service, but the condition needs to be corrected before it becomes more severe. |
Major |
|
A condition occurred that does impair service but not seriously. |
Critical |
|
A condition occurred that seriously impairs service and requires immediate correction. |