Contains the enumeration constants and the discovery routines for the LogVerbosity Extensible Enumeration.
More...
Contains the enumeration constants and the discovery routines for the LogVerbosity Extensible Enumeration.
◆ GetLogVerbosity()
int KIM::LOG_VERBOSITY::GetLogVerbosity |
( |
int const |
index, |
|
|
LogVerbosity *const |
logVerbosity |
|
) |
| |
◆ GetNumberOfLogVerbosities()
void KIM::LOG_VERBOSITY::GetNumberOfLogVerbosities |
( |
int *const |
numberOfLogVerbosities | ) |
|
◆ debug
The standard debug
verbosity.
The debug
verbosity level should be used when something normal and insignificant happened. Generic examples of a debug
condition include: a new user came to the site, a page was rendered, an order was taken, a price was updated. This is the stuff excluded from info
because there would be too much of it.
- See also
- KIM_LOG_VERBOSITY_debug, kim_log_verbosity_module::kim_log_verbosity_debug
- Since
- 2.0
◆ error
The standard error
verbosity.
The error
verbosity level should be used when the execution of some task could not be completed. Generic examples of an error
condition include: an email could not be sent, a page could not be rendered, some data could not be stored to a database, etc. Something has definitively gone wrong.
- See also
- KIM_LOG_VERBOSITY_error, kim_log_verbosity_module::kim_log_verbosity_error
- Since
- 2.0
◆ fatal
◆ information
The standard information
verbosity.
The information
verbosity level should be used when something normal but significant happened. Generic examples of an information
condition include: the system started, the system stopped, the daily inventory update job ran, etc. There should not be a continual torrent of these, otherwise there is just too much to read.
- See also
- KIM_LOG_VERBOSITY_information, kim_log_verbosity_module::kim_log_verbosity_information
- Since
- 2.0
◆ silent
◆ warning
The standard warning
verbosity.
The warning
verbosity level should be used when something unexpected happened, but that execution can continue, perhaps in a degraded mode. Generic examples of a warning
condition include: a configuration file was missing but defaults were used, a price was calculated as negative, so it was clamped to zero, etc. Something is not right, but it has not gone properly wrong yet - warnings are often a sign that there will be an error very soon.
- See also
- KIM_LOG_VERBOSITY_warning, kim_log_verbosity_module::kim_log_verbosity_warning
- Since
- 2.0