Application Logfiles

In the templates below, <instance> is the name of the OS user under which ServiceOptimizer is running.

Each ServiceOptimizer process creates an application log file named as follows: 

The FRU process also creates a separate Optimizer Log File: 

Initial set up

Default values are supplied for all logging within the system. Application Logfiles Formats and Sizes gives details as to why the settings are as they are, and how to change them if it is felt they need to be changed.

Why logging?

The best and most likely place to find information about a problem is stored in the log files.  This may indicate what the problem is, or at least give you an exact time when it occurred (you can verify the time of the crash by the timestamp of the log file). This information is invaluable to

• You - you can use Reading Log Files to help you understand their content and start off your investigations as to how to get your system back up and running healthily
• ServicePower - the Support team can use these files to help diagnose the problem and give insight into what solutions may be required. 

Logfile Management

The logfiles that are produced need to be managed to ensure they 

• useful in size and availability - archiving etc needs to ensure that files are available for follow up investigations perhaps several days after an issue/outage has occurred
• not causing adverse overheads on the system - creation of and existance of logfiles can impact both the performance of the system, and the stability of the system

Recovered Components discusses how the logfiles are managed on process failure.