Logging and Tracing Overview
SAP Mobile Platform provides supportability through logs and traces that enable administrators, developers, and support professionals to troubleshoot application issues. All logs have a common format and are stored in the SAP Mobile Platform Server database. All log entries for a particular business or application flow (such as an OData request or a registration) are correlated across the client and server stack. This enables you to visualize and understand the end-to-end flow, which helps in identifying the source of an application problem. In addition to logs and traces, you can activate end to end tracing on a per user/device basis to enable support to perform end-to-end diagnostics to identify performance or functional application problems.
System logs collect log messages that allow administrators and support professionals to identify problem areas. Developers can identify code problems by capturing debug level log messages. Set the log level for individual logging components to specify the amount of information captured.
Application tracing captures additional business data for a request (such as message data, payloads, HTTP headers, and URIs), which you can use to troubleshoot application problems. The business data captured in application traces is determined by the application developer. Enable tracing for individual logging components on an as-needed basis.
E2E tracing sessions are conducted by administrators and device users. E2E trace information is recorded in a Business Transaction XML (BTX) file on the client, which is uploaded to the server, and then uploaded to SAP Solution Manager for analysis.