Determining the root cause of a problem in a system that consists of a collection of products can be difficult. All products produce problem determination data, such as trace records, log records and messages. However, the problem determination data cannot be easily correlated across different products and products on different servers. Each product's problem determination data can only provide a view through a small window into the overall system problem. Timestamps are not sufficient: they are not granular enough and often clocks are not often sufficiently synchronized between servers. All of these problems make the job of problem isolation (that is, determining which server, which product, and what the root cause of the problem was) very difficult, and this complexity increases with the complexity and size of a system.
The Log Analyzer, which enables you to import various log files as well as symptom catalogs against which log files can be analyzed, decreases this complexity. The core issue in problem isolation in today's solutions is that problem determination data between products is not correlated, that is, you cannot easily determine the relationship of events captured by one product with the events captured by another. The Log Analyzer addresses this problem by now allowing you to import and analyze log files from multiple products, as well as to determine the relationship between the events captured by these products (correlation).
You have two different options for Log Analyzer
1) WebSphere Application Server Toolkit: You can switch to Profiling and Monitoring view in WebSphere Application Server Toolkit to access the Log Analyzer
2) The IBM Support Assistance also has Log Analyzer.