!--a11y-->
Session Tracing 
The Performance Tracing service provides a mechanism for dynamically activating traces for HTTP requests. Depending on the scope you have defined for the trace activity, it is possible that only the current HTTP request is traced, or all requests pertaining to the same HTTP session are traced.
You can enable the session tracing function using the Runtime user interface provided by the Performance Tracing service.
You must have enabled session tracing and configured the relevant settings as described in Enabling Session Tracing.
The system starts activity tracing for HTTP requests if the appropriate parameter is present in the request URL (by default, the name of this parameter is SAP-SAT; however, it is configurable and you can change its name as described in Enabling Session Tracing). You can provide two types of values for this parameter – one defining the scope of the traced activity, the other defining the trace level.
The value that defines the scope of the activity is mandatory. The possible values are:
Value |
Semantics |
scope-request |
Only the current HTTP request is traced. |
scope-session |
All consequent requests that pertain to the same HTTP session as the current request are traced. |
scope-none |
Deactivates traces for the HTTP session the current request pertains to. |
The value that defines the trace level is optional (by default, trace level is low). The possible values are:
Value |
Trace Module(s) to Activate |
level-low |
SQL trace |
level-medium |
DSR trace, SAT |
level-high |
Logging |
Note that the syntax of the above values is case-sensitive.
Consider also, that when you choose to use level-high, it applies the traces relevant for this level, plus the traces relevant for the lower levels. The same is valid for level-medium.

If you want to activate traces for HTTP requests pertaining to an HTTP session with trace level high, you have to use the following request URL:
http://<host>:<port>/<app_context_root>/<path>?SAP-SAT=scope-session,level-high
Note that if both values of the SAP-SAT parameter are provided, they must be separated by a comma.
If an HTTP request is part of an HTTP session, the latter is marked as debuggable. This implies that all consequent HTTP requests associated with that session are traced as well (no matter if their URLs contain the SAP-SAT parameter).

When parsing the HTTP request, the Web Container checks for the SAP-SAT parameter in the URL only. If the parameter is sent as a FORM parameter in the request body, it is ignored and activity tracing is therefore not performed for requests pertaining to the corresponding HTTP session.
A debuggable session ends when:
· The real HTTP session is invalidated
· You disable the session tracing function; disabling the function resets all debuggable sessions within the Web container
· You provide value of scope-none to the SAP-SAT parameter in the request URL.