This topic provides a brief description about the various log files that gets created under the <Web NMS Home>/logs directory.
List of Log Files
Following is the list of log files that appear in <Web NMS Home>/logs directory:
Description of Log Files
In this file, information about all the alerts that are updated through events are logged. New alert generation, alert deletion etc., are printed.
This log file is created whenever Service Pack update is performed. For example, if you update from Web NMS 4 + SP 1 to SP 2, this file is created. The update details are printed in this file.
In this file, the error/exception messages that appear (if any) while making a Service Pack update, are logged.
In this file, all discovery related happenings are logged. Addition/removal of Networks/nodes, starting of NetSearcher, nodes or networks discovered etc., are logged in this file.
MangementServer Framework related error messages are stored in this file.
ManagementServer Framework related output messages are stored here.
If Native Ping is enabled this log file is created. Information on Native Ping discovery is logged in this file. In Web NMS discovery, NativePing option is provided for querying device which is the Ping implementation in 'C' language. This is implemented to improve Ping performance while querying the device.
All important Web NMS related error messages are logged into this file.
All important Web NMS related output messages are printed in this file. This is quite a comprehensive log file which holds record of happenings right from server startup to the shut down. Module specific output message belonging to "POLL""POLICY" "TOPO"EVENT" "ALERT" "MAP" "CONFIG" "PROV" "MISC" "AGENT" "CLI" modules are logged by defult.
By default, System Error messages are directed to this file. That is, if you use System.err.println("<Message>") in your module, the error messages are directed to this file, by default.
By default, System Output messages are directed to this file. That is, if you use system.out.println("<Message>") in your module, the output messages are printed in this file, by default.
Whenever a client connects to the server, a check for compatibility of Web NMS version between server and client is done. In this file, the happenings during this check are logged.
All Prepared Statements obtained using the Web NMS Connection Pool are recorded in this file. By default, logging in transactionLogs.txt is disabled. To enable logging in transactionLogs.txt, edit log4j.xml file located in <Web NMS Home>/conf directory and set Logging="true" for the transactionLogs.txt entry.
This log file is created when Web NMS is started using Web NMS Launcher. All the messages that appear on the console while starting the server get printed in this file.
This log file is created when Web NMS is shut down from Web NMS Launcher.
This file is created when Web NMS is reinitialized from Launcher.
This file is created when Application Client is invoked from Launcher.
By default, some of the above log files are disabled. You need to enable them by configuring the log4j.xml file. For more details please refer to Logging Service.