Engage Engine API
1.246.9086
|
Variables | |
static const int | ENGAGE_LOG_LEVEL_FATAL = 0 |
A fatal error has occurred - Engine operation cannot continue. | |
static const int | ENGAGE_LOG_LEVEL_ERROR = 1 |
A error has occurred but operation can continue. | |
static const int | ENGAGE_LOG_LEVEL_WARNING = 2 |
Indicates that a condition exists that should be addressed soon. | |
static const int | ENGAGE_LOG_LEVEL_INFORMATIONAL = 3 |
The log message is of an informational nature - no action is required. | |
static const int | ENGAGE_LOG_LEVEL_DEBUG = 4 |
Debugging, primarily geared toward development and support personnel. | |
Logging levels dictate the amount of output generated by Engage during operation. In general you should aim to keep your logging at ENGAGE_LOG_LEVEL_INFORMATIONAL or lower as logging at ENGAGE_LOG_LEVEL_DEBUG produces a great deal of output and can overwhelm a system, resulting in degraded performance.
On systems that support syslog, Engage will output to the syslog subsystem so that monitoring tools can make appropriate use of messages - particularly those of a warning, error, or fatal nature.
|
static |
Debugging, primarily geared toward development and support personnel.
Definition at line 136 of file EngageConstants.h.
|
static |
A error has occurred but operation can continue.
Definition at line 130 of file EngageConstants.h.
|
static |
A fatal error has occurred - Engine operation cannot continue.
Definition at line 128 of file EngageConstants.h.
|
static |
The log message is of an informational nature - no action is required.
Definition at line 134 of file EngageConstants.h.
|
static |
Indicates that a condition exists that should be addressed soon.
Definition at line 132 of file EngageConstants.h.