Selecting CONSOLE SETs and specifying CONSOLE options and fields
For information about filterSpecifications, see FILTER-and-MATCH-parameters.
For information about severity, see Syslog-facilities-and-severities.
Parameter | Description |
|---|---|
CONSOLE | Must be specified as shown. |
FACILITY(facilityName) | Specifies the RFC 3164 facility that is to be indicated as the origin of the syslog messages corresponding to the indicated API1 event. If you omit this parameter, it defaults to LOCAL4. |
FIELDs(fieldName …) | Specifies the names of the EVENT CONSOLE fields that are to be transmitted to the BMC Defender Server or other syslog console, and the order in that they are to appear in the message. Specify one or more of the fields as described in Supported-record-field-names. |
filterSpecification | For information about filterSpecifications, see FILTER-and-MATCH-parameters. |
LOG | LOG(HEX) | Specifies that the selected CONSOLE event records are to be logged on CZAPRINT and optionally dumped in hexadecimal and character format. This parameter is intended primarily for diagnostic purposes. Use care in specifying LOG(HEX) as it might generate a large volume of print records, especially if BMC AMI Datastream is left running for several hours or more. |
PROCess(‘processTag’) | Specifies the tag that appears at the start of the syslog messages for CONSOLE events, following the priority, timestamp and hostname, and preceding the formatted fields. Specify the exact process tag that you want to include in syslog messages including any spaces and punctuation. Process-tag might be any length from the null string (‘’) to 32 characters. If PROCess is omitted, it defaults to CONSOLE, followed by the leading delimiter from OPTIONS DELIM. |
SELECT(setName ...) | Specifies one or more console message sets that are to be selected for processing. Console messages are tested for qualification for sets in the order specified; the first matching set ends the search. |
SEVerity | Specifies the syslog severity of the selected console message For information about severity, see Syslog-facilities-and-severities. |