End-to-End Trace Plugin
(Android, iOS, Windows 8.1, and Windows 10) Handles end-to-end tracing in Hybrid SDK (Kapsel) applications.
Enabling application tracing captures additional data for a request (such as payload, HTTP headers, and URIs), which can be used to troubleshoot application problems. The data captured in application traces is determined by the application developer. You can set the logging level using the setTraceLevel() method. You enable tracing of HTTP requests using the enable startTrace( [transactionName] ) method. Data is recorded for the transaction between when you start the trace and when you turn off the trace by the endTrace() method. Kapsel treats the entire session as a single transaction. The following information is recorded for each XMLHTTPRequest:
- the total time taken (start time and end time of the request)
- the headers for the request
- a status code for the response (such as 200 if successful)
End-to-end tracing sessions are conducted by administrators and device users. End-to-end trace information is recorded in a Business Transaction XML (BTX) file on the client. Logs and traces are synchronized with the server when you initiate an upload using the uploadTrace() method, and you can then upload the data to SAP Solution Manager for analysis.
For more information, see the following topics in Developer > Native OData Application Development:
- Logging and Tracing Overview
- Supportability for iOS
- Supportability for Android
- Supportability for Windows