A handle level (or severity level) enables you to specify the level of detail of the information stored in the log file. This also enables you to control the rate at which the log file will grow.
You need to use the HandleLevel parameter in the WebClient.ini file to set the log levels in the log file. The following table describes the values that the HandleLevel parameter supports:
|
Log Level |
Description |
|
|---|---|---|
|
1 |
debug |
Use this log level for logging detailed information for debugging purposes. This might include process tracing and changes in Server states. |
|
2 |
info |
Use this log level for capturing information on run-time events. In other words, this information highlights the progress of the application, which might include:
|
|
3 |
notice |
Use this log level for checking the ArcotID PKI Client status and version. |
|
4 |
warning |
Use this log level for undesirable run-time exceptions, potentially harmful situations, and recoverable problems that are not yet FATAL. |
|
5 |
error |
Use this log level get information about failures in functionality that occur due to the data in unsupported format. For example, parsing corrupt ArcotID PKI files, or corrupt key and certificate data. |
|
6 |
alert |
Logs of this level are currently not generated by the ArcotID PKI Native Client. |
|
7 |
fatal |
Use this log level for serious, non-recoverable errors that can cause abrupt termination of the AuthMinder service. |
Note: When you specify a log level, messages from all other levels of higher significance are reported as well. For example if the HandleLevel is specified as 3, then messages with log levels of debug, info, and notice level are also captured.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|