Debug settings and corresponding syslogd priority levels
Table 1 summarizes the available
debug levels and their associated syslogd priority levels.
| Logging category/Level | Description |
|---|---|
| None — 0 | No messages of any kind are sent to the logging file after initialization is complete. |
| ERROR — 1 | Error messages indicate something that requires
attention. Messages at this level could be fatal (terminating) or
could indicate that an important part of the workload advising system
is not working properly. This information is logged at the syslogd ERROR priority level. |
| WARNING — 2 | Warning messages indicate that an error has
occurred, but it is not severe enough to warrant an ERROR. Corrective
action might be necessary because the Advisor or Agent might not be
behaving as intended. This information is logged at the syslogd WARNING priority level. |
| EVENT — 4 | Event messages are logged for things that happen
periodically, like operator commands, UNIX signals, timer pops, receipt of a network message, and
so on. This information is logged at the syslogd NOTICE priority level. |
| INFO — 8 | Informational messages are sent to the logging
file. These messages do not require corrective action. This information is logged at the syslogd INFO priority level. |
| MESSAGE — 16 | Message messages concern the detailed contents
of message packets that are sent between the Advisor and LB, or between
the Advisor and Agent. These can be used to assist debugging Advisor/LB
and Advisor/Agent communications. This information is logged at the syslogd DEBUG priority level. This level is intended for IBM® service use only. |
| COLLECTION — 32 | Collection messages concern the details of collecting
and manipulating the data that forms the basis of weight calculations.
This information is logged at the syslogd DEBUG priority level. Restriction: COLLECTION is only used by the Agent.
This level is intended for IBM service use only. |
| DEBUG — 64 | Debug messages are intended for Development
or Service and give detail that customers would not normally want.
The intention of this level of message is to provide information
that is useful in debugging code, logic, or timing errors. This information is logged at the syslogd DEBUG priority level. This level is intended for IBM service use only. |
| TRACE — 128 | Trace messages are intended for Development
or Service to track code processing (footprints). This information is logged at the syslogd DEBUG priority level. This level is intended for IBM service use only. |