Log Types and Formats 
The Log Viewer tool supports the following log types and formats:
Log Types |
Log Formats |
|---|---|
ListLog |
List |
ASCIILog |
Text; Trace |
SysLog |
ABAP Sys Log |
You cannot configure the log types and formats.
Note
The Message field in Log Viewer has maximum size of 64 KB.
This is a standard human readable format that can be parsed and is used by the Log Viewer and AS Java. List formatted logs are written to a file whose values are separated by a hash (#).
For more information, see List Log Format 2.0
There is a specific list formatted log file called Change Log. It gives information about all configuration changes made on the AS Java. It also shows the ID of the user who has made the change. The log file path is: <SAP_install_dir>/<system_name>/<instance_number>/j2ee/cluster/changelog.
For example:
Syntax
#2.0#2008 04 15 16:43:09:687#+0300#Info#/System/Changes/configtool# ###C0000A37462200010000000301BE2893###configtool########Thread[Thread-5,5,main]#Plain## Value of property ArchiveOldLogFiles was changed from OFF to ON for Instance - ID543210, manager - LogManager.# #2.0#2008 04 15 18:47:29:778#+0300#Info#/System/Changes/configtool# ###C0000A37462200020000000201BE2893###configtool########Thread[Thread-6,5,main]#Plain## Number of debug nodes was changed from 1 to 1 for Instance - ID543210#
This format is relevant for text log files and has random structure. For example:
Syntax
<!--LOGHEADER[START]/--> <!--HELP[Manual modification of the header may cause parsing problem!]/--> <!--LOGGINGVERSION[1.5.7.1006]/--> <!--NAME[D:\usr\sap\LKG\J00\work\deploy.trc]/--> <!--PATTERN[deploy.trc]/--> <!--FORMATTER[com.sap.tc.logging.TraceFormatter(%25d[%s] %m)]/--> <!--ENCODING[UTF8]/--> ... <!--LOGHEADER[END]/--> Apr 24, 2008 12:48:16 PM [Info ] [Server 00 00_37057] (11354) :Deployment status of [sap.com_ATSFormalTestApplication365900472] was changed from [Delivered] to [Success] [ASJ.dpl_dc.006301] ... Additional information: ] [ASJ.dpl_dc.001048] ...
This format is the same as text format. However, it has a particular structure. For example:
Syntax
%24d %-40l [%t] %s: %m
where,
%d is a timestamp in a readable format.
%l is the location on behalf of which the message has been created.
%t is the thread that has emitted the message.
%s is the severity of the message.
%m is the message text.
The numbers in the pattern denote the number of characters for an item. The corresponding output is the following:
Syntax
Dec 01, 2007 10:10:00 PM com.sap.FooClass.fooMethod [main] Fatal: A sample fatal message