-
Request for existing cases, user IDs, Portal navigation support and more
Using Trace Analysis
In order to use the E2E Trace Analysis in SAP Solution Manager, you need to specify which systems should be used. This can be done with the Scope Selection.
Scope Selection
When starting initially the trace application from the Launchpad a scope a probably not set. You can do this by clicking on the Scope Selection icon in the header of the shell.
You can save multiple queries of systems you want to analyze. When the flag 'Set as Default' is set, this query is your default query. The flag 'Execute on Select' specifies if this scope selection should be used when you start the application the next time. By setting the 'Share' flag other users can use this scope selection too.
Performing a trace can be separated in four general steps:
- Enabling
- Recording
- Collection
- Evaluation
Allow Tracing in the Managed Systems (Trace Enabling)
In the trace application tracing for all selected managed systems can be allowed centrally on the page Trace Enabling.
The screen shot above displays the tracing status for the two J2EE systems FBJ and FSJ and the ABAP systems FBT and FQ7_SM. In this case tracing is allowed for the ABAP systems but not for the J2EE systems. Possible states are:
The screenshot above displays the tracing status for the two J2EE systems FBJ and FSJ and the ABAP systems FBT and FQ7_SM.
In this case tracing is allowed for the ABAP systems but not for the J2EE systems.
Possible states are:
Tracing is enabled and allowed in that system
Tracing is disabled and not allowed in that system
Trace Status is unknown. See details in error message or in default.trc of the Solution Manager Diagnostics.
In progress, Trace status is currently read
With the button Enable all tracing will be allowed for all systems in this scope.
For each system the status can be toggled.
Explanation of Trace Levels
Trace Level Low
Only statistical records and HTTP log entries are written. HTTP logs are required for HTTP analysis providing frontend, server response times (HTTP logs) and derived network times. Statistical records are utilized to show the relationship between different managed systems and to show how much time is spent on each system. No server-side traces are triggered in this case and thus the performance overhead is very low. Use this trace level if you want to do performance measurements.
Trace Level Medium
This trace level represents a performance trace. In the table below you can see which traces are triggered when using this trace level. Use this trace level when you have identified a performance bottleneck and you want to do a drill-down.
Trace Level High
This Trace level represents a functional trace. This could have significant impact on the response time. The following table gives an overview of the traces written per trace level for SAP J2EE:
Trace Level | HTTP Log | SQL Trace | Logging | Introscpe Transaction |
---|---|---|---|---|
Low | X | |||
Medium | X | X | X | |
High | X | X | X | X |
The following table gives an overview of the traces written per trace level for ABAP.
Trace Level | HTTP Log | SQL Trace | ABAP Trace (SAT) | Application Log (SLG1) |
---|---|---|---|---|
Low | X | |||
Medium | X | X | Aggr. | |
High | X | X | Non aggr. | X |