For a particular log-handler, the active status of a logging level is determined by a set of factors.
Table 9-5 lists these factors.
Table 9-5 Factors that Determine Whether Logging Is Active
| Factor | Importance | Description |
|---|---|---|
|
|
Primary |
This parameter sets a cutoff for logging. Any log level that is more detailed than the threshold is suppressed. See Table 9-1 for valid log levels. You override this parameter for a subset of items that can be logged using the |
|
|
Primary |
This sets a per-module override for the global logging threshold. See "Configuring Different Threshold Levels for Different Types of Data" for details. |
|
|
Secondary |
This parameter toggles logging on or off, as long as it is not overridden by the logging threshold or a module-specific override. |
|
The physical position of a log handler |
Secondary |
See "About Log Handler Precedence". |
You can configure up to three log-handler definitions for a single log level in a log configuration file.
Three different log handlers are required to send output for a particular log level to each of the three log writers described in Table 9-3.
If you specify different LOG_STATUS settings in these log handlers, the setting in the log-handler definition closest to the physical end of the log configuration file sets the status for the other log-handler definitions of the same log level. For example, you can set LOG_STATUS to Off for the first two log handlers for the Error log level, but if LOG_STATUS is On for the third and final log handler in the configuration file, logging still occurs for all three handlers.
The LOG_STATUS settings are moot if that level is more fine-grained than the current LOG_THRESHOLD_LEVEL. In this case, logging cannot be activated at this level unless the threshold is overridden by a module-specific threshold. See "Configuring Different Threshold Levels for Different Types of Data" for details.