IBM Tivoli Netcool/Impact 7.1.0

Monitoring deployment components and logs

Netcool®/Impact provides a centralized logging feature that incorporates Apache Log4j logging functionality.

Monitoring server instances
You can monitor and log the status and activity of both the Impact Server and the GUI Server.
Customizing logging and tracing settings
To change the default behavior for logging and tracing, you must edit the default values in the log property files for both the Impact Server and GUI Server.
Monitoring services
Services running in the Impact Server can print their activity and status messages to a log file. You can control the number of log files that are produced and their size.
Controlling the creation of service log files
You can control the maximum size of log files and the number of log files that are created on a service by service basis.
Controlling the creation of policy logger files
You can change the maximum size of the policy logger log file, control the number of policy logger files that are created, and change the permissions set for the policy logger files.
Event processing and locking
Debug logging for event processing and locking can be switched on dynamically. This means a server restart is not required for the changes to the log4j properties file to take effect.

Parent topic: Post installation steps