After you have created a Single Activity Trace, you can import the trace results for the local instance into the database, and display traces that were imported into the database across all systems.
On the initial screen of the VMC System Administration (SM53) in the structure on the left side under Navigation choose Single Activity Trace → Results.
Import lokaler Trace-Daten in die Datenbank...
The status display in the header area shows the following information:
● Number of Imported Trace Records: This is the trace data already written to the database. They are entered in a list beneath the header area.
● Are there other trace records that have not been imported?
Here you can see whether for this instance there is any trace data that has been written to the file system, but not yet imported into the database. In this case you can start the import. Choose Import Trace Records.
Note that local data from the file system cannot be partly imported into the database. You can only import the entire local data in one go.
If the trace data is not relevant, you can delete it. Choose Delete All Local Trace Data.
You can reset the entire database. Choose Delete All Trace Data.
Beneath the header area is the list of all the imported trace records. It contains the following information for each trace record (columns):
Column |
Meaning |
Executed on |
Start time of the request for which the trace is created |
Total time |
Duration of the executed actions |
User |
User who performed the action |
Level |
Number of components included in the trace 1: System layer only 2: System layer and application layer 3: System layer, application layer, and database layer |
PM |
VM, in which the action(s) were performed (see VM Overview) |
RFC module |
RFC module for which the trace was created |
Session |
Associated session (see Displaying and Managing Sessions) |
Transaction ID |
Associated transaction ID (see Single Activity Trace) |
By double-clicking on a record you can see the trace data.
The detail information of a trace entry is made up of meta data and metrics. The meta data is provided by the SAT infrastructure, for instance, the environment in which the trace was generated. The metrics on the other hand are created by the developers in their code, whereby certain metrics are generated by the VMC infrastructure (prefix: jts) for each trace.
In the header bar you can set filters for the trace hierarchy. The filters relate to the infrastructure layers (system, application, database) and enable the traces from a selected layer to be displayed. The two windows at the bottom display the progress of the trace. On the left side is the trace hierarchy, and on the right side is the detail information of a trace entry selected from the hierarchy.