Setting error_level in log_collect ConfD job doesn't work
Details
| Detail name | Value |
|---|---|
| Changelog Number | 20327 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.0.0 |
| Fix Versions | Exasol 8.29.8, Exasol 8.34.0 |
| Resolution Date | 2025-03-10 |
Description
The log_collect ConfD job can be used to collect and display log messages according to various filtering criteria. Among them is the severity of the messages (such as WARN or ERR), which can be specified using the error_level job parameter (so that entries with a lower priority, such as INFO if error_level is set to WARN, will not be displayed). Due to a bug in the implementation, this does not actually work though; using error_level as documented causes the job to crash with
ERROR: HTTP 500: TypeError('can only concatenate str (not "int") to str')
Workaround
Do not set error_level.
Fix
Setting error_level has the expected effect of filtering out log entries with a lower than specified severity, and the job does not crash.