| Field | Description |
| Example |
|---|
| Date | Date when request was received. | Fields Date and Time are set automatically for system messages.
Custom log messages written with the Log Adapter or the report can contain a custom timestamp. This may result in log messages that are not sequential. | 2018-06-06 |
| Time | Time when request was received. | 08:02:45 |
| Time Zone | Time zone offset | +0200 |
| Transaction ID | Unique ID of the transaction. It is used to trace service calls through the call stack (see Transaction ID). The transaction log contains the first 40 characters of the transaction ID. | 00000002d3b0bdc0000069ce00ff9700ea65376f |
| Request ID | Unique ID of request. It will be reset when restarting the xUML service. | 101 |
| Component Name | Name of component that has been requested (not the name of the xUML service). | urn:Services.SupportCase.SupportAPI.supportcases.GET |
| Elapsed Time | Elapsed time, for each call (service calls, external or internal calls) in milliseconds. If the elapsed time is displayed as "0", the logged step has taken below 1 millisecond of time. The value of elapsed time does not contain: before SERVICE_ENTER after SERVICE_EXIT
| 36
|
| State | State is either OK or ERROR. | OK |
| Domain | - If an adapter has been called, the domain fields contains a value denoting the adapter, for instance SAPRFC, SQL, FILE, SYSAD, POP3, URL, etc.
- If a service operation has been called, the value is INTERFACE.
- If a log entry has been triggered by the user via the logger adapter, the value was defined in the UML model.
| INTERFACE
|
| Log Type | - SERVICE_ENTER or SERVICE_EXIT marks the begin/end of a service call.
- TRANSITION_ENTER or TRANSITION_EXIT marks the begin/end of persistent state transition handling.
- DOACTION_ENTRY or DOACTION_EXIT marks the begin/end of a persistent state do activity.
- IO_ENTER or IO_EXIT marks the begin/end of an IO operation, like e.g. an adapter call.
- If the logger adapter triggered the log entry, the value is CUSTOM.
| SERVICE_EXIT |
| Parameter 1 and 2 | - Parameters, for instance, if the file system adapter has been called, the first parameter corresponds to the executed action (e.g. ReadDirectory) and the second one to the specified file.
- If the logger adapter triggered the log entry, the first parameter corresponds to the description defined as input for the adapter in the UML model.
| anonymous 2.0.232.75
|
| Correlation ID | Unique ID that relate an adapter call with the adapter response. The transaction log contains the first 40 characters of the correlation ID. A correlation ID is available for the following: - adapters sending a correlation ID: SOAP, URL, SMTP, SAPRFC, Persistent State, JMS
- services receiving a correlation ID: SOAP, HTTP, SAP, JMS Listener
For more information refer to the adapter pages. | 00000011e33a4f8400004fc4000043ac9bc69bee |