Log Types (SAP Library - Administration Manual)

Log Types

The following are the log types available for Log Viewer:

· ListLog

· ASCIILog

· SQLTrace

· SAPJTrace

· SAT Trace

This graphic is explained in the accompanying text

The log types are not configurable.

Log Formats

Messages can be configured to be output in different formats. You can configure the formats through the Log Configurator. Following are the different log formats supported by the Log Viewer:

· Trace format

· List format

· ASCII format

· SQL Trace format

· SAT Trace format

Trace Format

This is the most commonly used, non-parsable format for users to glance through and quickly diagnose the output content. By default, the pattern is (format created by the developer in the configuration of the component):

%24d %-40l [%t] %s: %m

and the corresponding output is:

Dec 01, 2003 10:10:00 PM com.sap.FooClass.fooMethod [main]
Fatal: A sample fatal message

List Format

This is a standard parsable format used by the Log Viewer and the J2EE server. It is written to a file as simple hash-separated fields.

Example

#1.3#10.48.27.165:4A5AB2:E99D42D4F4:-8000#Mon Dec 01 22:00:00 PDT2003#com.sap.FooClass#com.sap.FooClass.fooMethod#main##0#0#Fatal##Plain###A sample fatal message

SQL Trace Format

An example of such a format is as below:

<log>

<thread>Thread-58</thread>

<msg-clear>DELETE FROM "J2EE_CONFIGENTRY" WHERE "CID" = ? AND "ISFILE" = 0</msg-clear>

</bindparams>

<dbid>jdbc:sap:sapdb://lw1021/JAVA?timeout=0?DEV1401</dbid>

<location>com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch</location>

</record>

</log>

ASCII Format

This type of a file can be any text file with no particular format. It is the same as Trace format.

SAT Trace Format

The Single Activity Trace (SAT) log files are displayed in a format different from general logs. When displaying an SAT file the whole file gets read. This is necessary because the SAT records have to appear in a certain order. It looks similar to List format.

Turn on Traces for Users

In SAT Administration section in the portal, turn on traces for the required users, specifying users by name and user ID. See Portal Platform à System Administration à Monitoring Technology and Logging à Activity Tracing in the SAP EnterprisePortal AdministrationGuide. This guide is located on SAP Help Portal at http://help.sap.com/ep).

Viewing a SAT Log

Choose the SAT file. The SAT trace file is displayed by the Log Viewer.

For the SAT three different record types are shown:

· request

· component

· action

The fields that can be displayed are listed in the following table in alphabetical order by field name. The default fields are marked as such under the Display column.

Field	Display	Origin	Description
Application	Optional	Log	Name of the running application
Class Name	Optional	SAT	Name of the class which hosts the measured activity
Class Version	Optional	SAT	Version of the hosting class
Datasource	Optional	Log	The log file name and the cluster ID of the cluster on which the log resides
Date	Optional	Log	The date when this log record was created
Description	Default	SAT	Short text description of measured activity.
DSR Component	Optional	Log	Name of the component given in the correlator for distributed transactions
DSR Transaction	Optional	Log	Name of the DSR (Distributed Statistics Record) transaction
GrossTime	Default	SAT	Total elapsed duration in milliseconds of the activity. An error condition is indicated by “-1”.
Level	Default	SAT	The nesting Level indicating how deep the component is nested. A “0” means the main level. JARM Request indicates nesting level “-1”.
Location	Optional	Log	Where the record came from – usually the class name.
Message	Optional	Log	The clear text version of this log record. This is typically the message written out by the program.
Message ID	Optional	Log	The message identification of this log record. The unique identification is written to logs via most formatters and allows for unambiguous cross-referencing among messages in different logs.
Name	Default	SAT	The name of the measured activity.
Net Time	Default	SAT	The total elapsed time in milliseconds of the activity; this is the gross time minus the time that was spent in sub calls. It is only available with Record Type JARM Component. An error condition is indicated by “-1”.
Number of Sub Records	Optional	SAT	Number of subrecords JARM Request: number of included components JARM Component: number of included actions
Out Data	Default	SAT	For future use..
Record Type	Optional	SAT	One of the following record types: 10 – JARM Request 11 – JARM Component 12 – JARM Action 20 – DSR Action (for future use) 21 – DSR External Call (for future use) 22 – DSR Internal Call (for future use) 23 – DSR Trace 30 – TREX Trace
Sequence Number	Optional	SAT	The Sequence Number, which starts with 0. It depends on the Record Type: JARM Component: indicates the call sequence of the components JARM Action: indicates the call sequence of the actions JARM Request: not available
Session	Optional	Log	The name of the session in which this activity executed
Severity	Optional	Log	The severity of this log record. (For example, Error, Warning, Info, etc.)
Source Name	Optional	Log	The name of the log controller this log record came from
StartTS Date	Optional	SAT	Start time stamp of activity; the date since midnight, January 1, 1970 UTC
StartTS Time	Default	SAT	Start time stamp of activity; gives the time since midnight, January 1, 1970 UTC.
State	Optional	SAT	The status of activity. 0 – status OK 1 – activity not closed properly 2 ‑ overflow
Thread	Optional	Log	The thread this log record belongs to if it still runs
Time	Default	Log	The instantiation time of this log record in milliseconds
User Name	Default	SAT	The name of the user given in the code

Example of SAT Log

This graphic is explained in the accompanying text