Kanzi  3.9.9
Kanzi Engine C++ API
Log levels

Use log levels to classify log messages based on the severity of the information that they carry. More...

Collaboration diagram for Log levels:

Macros

#define KZ_LOG_LEVEL_ERROR
 Use the error log level to log critical malfunction messages. More...
 
#define KZ_LOG_LEVEL_INFO
 Use the info log level to log information messages that give a brief overview of what is happening in the system, log states passed, static information about configuration, and so on. More...
 
#define KZ_LOG_LEVEL_TRACE
 Use the trace log level to get the maximum amount of information about the system. More...
 
#define KZ_LOG_LEVEL_WARNING
 Use the warning log level to log facts that require attention, but do not necessarily mean malfunction. More...
 

Detailed Description

Use log levels to classify log messages based on the severity of the information that they carry.

These are the log levels available in the Kanzi logging subsystem:

Log level Severity value Name
KZ_LOG_LEVEL_ERROR 1 error
KZ_LOG_LEVEL_WARNING 2 warning
KZ_LOG_LEVEL_INFO 3 info
KZ_LOG_LEVEL_TRACE 4 trace

Macro Definition Documentation

#define KZ_LOG_LEVEL_ERROR

Use the error log level to log critical malfunction messages.

Because the purpose of error messages is to provide as much information as possible needed to investigate the reported issue, it is recommended to make error messages very detailed.

#define KZ_LOG_LEVEL_WARNING

Use the warning log level to log facts that require attention, but do not necessarily mean malfunction.

For example, use a warning message to notify the user about something recoverable, such as a missing parameter that has the default value, or something that can lead to performance degradation, but not failure.

#define KZ_LOG_LEVEL_INFO

Use the info log level to log information messages that give a brief overview of what is happening in the system, log states passed, static information about configuration, and so on.

#define KZ_LOG_LEVEL_TRACE

Use the trace log level to get the maximum amount of information about the system.

This is the most verbose log level, mainly used to troubleshoot issues.