Skip to content

Logging Overview

Managing issues with apps rolled out to a large number of users is a challenge and often requires deep insights into running applications to troubleshoot. For that purpose, Mobile Services includes a Logging feature that enables you to gain insights into live apps. Use our SDKs to gather logs on client devices, to add contextual information and to automatically or manually upload them to Mobile Services for further inspection. Leverage the Mobile Services cockpit to gain an integrated insight into your user base, regardless the platform on which the issue originally occurred, and to access raw log data for further analysis in dedicated tools. Choose from the below platform options to get started now!

AndroidAPIsAdministration

Feature Scope

Feature Description
Gather client logs The SAP Cloud Platform SDKs and Mobile Development Kit by default log certain actions, which can be made visible by means of configuration. In addition, they allow you to log custom messages on different levels of severity. Both standard SDK and custom logs can be uploaded to Mobile Services for remote inspection and analysis.
Gather server logs Mobile Services has a wide range of logging options that can be configured on the component level. Use the web interface to set log levels per component.
View technical and event logs Both uploaded client and server-side logs can be inspected in a dedicated web interface that offers an array of filters to bring order to the variety of logs gathered. In addition, event logs are provided, which aggregate complex business operations that would otherwise result in an abundance of separate service calls and hence technical log entries.
Download gathered logs For further analysis with specialized tools, Mobile Services lets you download arbitrary subsets of gathered logs to your computer.
Archive logs In order to focus on recent events, Mobile Services automatically archives logs that exceed a certain threshold. Use the dedicated log settings to configure what kind of logs should be archived, and when.
Auditing Traceability of changes in an enterprise world is key, which is why Mobile Services by default tracks changes to all settings and exposes an activity log that can be filtered in a number of ways. An export option is available for further processing.

Procedure

  1. Enable log uploads for your application in Mobile Services
  2. Integrate the logging feature of the SDKs into your application
  3. Gather logs in your application
  4. Upload the logs to Mobile Services or let the SDKs handle it automatically
  5. Inspect and analyze logs in the Mobile Services cockpit
  6. Customize logging and log upload policies in Mobile Services

Log Types

Logs fall into two categories:

Event Logs: Generated by the server and provide information about the activities of mobile application users. By default only warnings and errors are logged. These contain information about any problems that a mobile application user has experienced. This could be a problem with requesting data from a back end, for example. To also view success messages, enable them for each application and assigned feature. See Viewing Event Logs for additional information.

Client Logs: Generated by mobile applications and uploaded to the server. These can be enabled for each mobile application by activating the Mobile Client Log Upload feature (see Configuring Mobile Client Upload for additional information) . Based on the configuration, mobile applications can upload log files to the server and an administrator can download them for problem investigation.

User Logging

Unique names are generated for anonymous users, and the anonymous users are included as "active users" or "users" for metering. Anonymous users are counted as "active users" or "users" per device, depending on the license type upon which Mobile Services is running.

An active user is an individual user of a platform application that connects to the Cloud service at least once during any rolling three-month period. Each active user may only access the Cloud service via a single platform application. An individual accessing the Cloud service via more than one platform application is counted as a separate active user for each platform application.


Last update: August 12, 2020