List Log Format 2.0 
This is a standard human readable format that can be parsed and is used by the Log Viewer tool and AS Java. List format 2.0 logs are written to a file and its fields values are separated by a hash (#).
Features
General characteristics of List log format 2.0:
Fields are delimited by # ( sharp ) character
Log record is split among several lines
Log record does not have a fixed number of fields (columns)
The following table describes technical details about List log format 2.0:
Parser state |
Pos |
Field name |
Example value |
Optional |
Default |
Description |
|---|---|---|---|---|---|---|
1 |
1 |
Version |
2.0 |
No |
2.0 |
SAP Logging API version This value is used for defining parsing procedure version. |
2 |
2 |
DateTime |
2010 01 08 14:30:36:084 |
No |
Date & time in format: YYYY MM DD HH:MM:SS:mmm |
|
3 |
3 |
TimeZone |
+6:30 |
No |
Time zone in format +/-N:NN (where N is an integer number) |
|
4 |
4 |
Severity |
INFO |
No |
DEBUG, PATH, INFO, WARNING, ERROR, FATAL |
Severity of the log record |
5 |
5 |
SourceName |
com.sap.mycomponent or /System/Database |
No |
Location or Category name |
If the log record was written using Category, then value is equal to that Category name. If Location was in use, value is equal to the Location name. |
6 |
6 |
MsgCode |
web:0a0067 |
No |
Unique message ID used in MessageID concept |
|
7 |
7 |
CSN Component |
BC-JAS-ADM |
No |
Empty string (“”) |
Component in the Customer Service System to which this message is related |
8 |
8 |
DC Component |
tc/lm/webadmin/performance/viewer/wd |
No |
Empty string (“”) |
Development component |
9 |
9 |
GUID |
000FFE93A54F002700000683000018B401228AEE |
No |
GUID value |
Unique log record ID |
10 |
10 |
Correlation ID |
000FFE93 |
No |
Correlation ID |
Implicit properties from AS Java |
11 |
11 |
Application |
MyApplication |
No |
Empty string (“”) |
Implicit properties from AS Java |
12 |
12 |
Location |
com.sap.mycomponent |
No |
Location name |
Mostly, class or package name where the log record is created |
13 |
13 |
User |
MyUser |
No |
Empty string (“”) |
Implicit properties from AS Java |
14 |
14 |
Session |
MySession |
No |
Empty string (“”) |
Implicit properties from AS Java |
15 |
15 |
Transaction |
MyTransaction |
No |
Empty string (“”) |
Implicit properties from AS Java |
16 |
16 |
DSRRootContextID |
38fe6ce0639411dc96dd000ffe93a2aa |
No |
Empty string (“”) |
Implicit properties from AS Java |
17 |
17 |
DSRTransaction |
38fe6ce0639411dc96dd000ffe93a2ab |
No |
Empty string (“”) |
Implicit properties from AS Java |
18 |
18 |
DSRConnection |
38fe6ce1389411dc96dd000ffe93a2cc |
No |
Empty string (“”) |
Implicit properties from AS Java |
19 |
19 |
DSRCounter |
20 |
No |
Empty string (“”) |
Implicit properties from AS Java |
20 |
20 |
ThreadName |
System [28] |
No |
Main |
Thread name |
21 |
21 |
MsgType |
JAVA |
No |
PLAIN |
Log record message types:
|
22 |
22 |
ResourceBundle |
MyResourceBundle |
No |
Empty string (“”) |
Resource bundle name |
23 |
23 |
MsgText |
Server {0} will be down in {1} minutes! |
No |
Empty string (“”) |
Message |
24 |
24 |
MSGArgsNo |
2 |
YES |
Number of arguments in the message (e.g. 2) |
|
25 |
24+1 |
MSGArg_1 |
MyServer |
YES |
First message argument |
|
26 |
24+2 |
MSGArg_2 |
15 |
YES |
Second message argument |
|
27 |
24+n |
MSGArg_n <= MSGArgsNo |
... |
YES |
Next (N) message argument |
Note
All expected fields are shown on new line.
Empty string values are expected as “”.
Empty numeric values are expected as -1.
Example
#2.0#2010 01 08 14:30:36:084#+6:30#INFO#com.sap.mycomponent#web:0a0067#BC-JAS-ADM#tc/lm/webadmin/performance/viewer/wd#
000FFE93A54F002700000683000018B401228AEE#000FFE93#MyApplication#com.sap.mycomponent#MyUser#MySession#MyTransaction#
38fe6ce0639411dc96dd000ffe93a2aa#38fe6ce0639411dc96dd000ffe93b1cc#38fe6ce0639411dc96dd000ffe93d345#20#System [28]#
JAVA#MyResourceBundle# Server {0} will be down in {1} minutes!#2#MyServer#15#