Setting the logging level

You can change the logging level to provide more detailed log or trace files to help with debugging MIB Manager. The extra information provided by increasing the logging levels can help you when debugging specific problems when parsing MIBs.

To change the logging level, click Edit > Debug from the main window menu bar. Log files have six message levels that you can cycle through to increase the level of detail that is captured: none, error, warn, info, debug, and verbose.

The following table provides a brief description of each logging level:

Table 1. A list of logging levels with their associated description
Log level	Description
none	Specifies a log level in which no debug messages are output. The performance of the application is improved but no warning or error messages are displayed during parsing.
error	Specifies a log level in which only errors which affect the results are logged. This includes any error identified by MIB Manager which would result in incorrect data being displayed in the main window.
warn	Specifies a log level in which warning and error messages are logged. A warning indicates a condition that could result in erroneous data and therefore must be checked. However, the condition will not cause the data to be corrupted.
info	Specifies a log level in which informational, warning, and critical messages are logged. Informational messages contain detail regarding overall task progress. For example, they provide the complete text for objects as they are being parsed.
debug	Specifies a log level in which all messages are logged. Note: Only run MIB Manager in debug mode when you are attempting to resolve and error condition. The volume of data produced while parsing only a moderate number of MIBs will quickly fill your file system.
verbose	Specifies a log level in which all information messages are logged. A verbose message includes the state of variables, arrays, and hashes as they change value and state.