Log Levels
Log levels control the behavior of the log writer at runtime.
They are a custom construct, that strongly correlates with the "Problem Classes" used by SAPs standard logging API to express the severity of a log message.
| Log Level | Corresponding Problem Class | Logged Problem Classes | Description |
|---|---|---|---|
| 0 | N/A | NONE | Log is completely deactivated. |
| 1 | '1' (Very important) | '1' | Minimum severity: Very important |
| 2 | '2' (Important) | '1', '2' | Minimum severity: Important |
| 3 | '3' (Medium) | '1', '2', '3' | Minimum severity: Medium |
| 4 | '4' (Additional Information) | '1', '2', '3', '4' | Minimum severity: Additional Information |
| 5 | ' ' (Other) | '1', '2', '3', '4', ' ' | Minimum severity: Other |
| 6 | N/A | '1', '2', '3', '4', ' ' | Additional escalation level. Needed to control creation of data containers. |
The logging API knows different types of Log Levels:
| Log Level Type | Database Table | Description |
|---|---|---|
| Product specific | /USI/BAL_LV_LOBJ | Customized by the developer. Defines the bare minimum that needs to be logged no matter what. |
| User specific | /USI/BAL_LV_USER | Current setting (maintained directly in production). |
| Client specific | /USI/BAL_LV_CLNT | Current setting (maintained directly in production). |
| Effective | N/A | Combination of previous Log Levels at runtime. The highest Log Level always "wins". |
