Skip to content

Setting Server Log Levels

You can change the logging level for one or more logging components. In a troubleshooting situation, you may want to increase the log level to capture more details.

Context

Note

Logging detailed information consumes system resources, so SAP recommends that you change the log level only when you suspect a serious problem, or are testing a theory. In most situations, it is sufficient to log only errors and warnings.

Procedure

  1. In Mobile Services cockpit, select Settings > Log Settings.
  2. For each component, select a log level.

    System Logging Components

    Component Description
    Admin Logs system messages that are related to SAP Cloud Platform Mobile Services administration.
    Cloud Build Logs system messages that are related to the cloud build service.
    Connectivity Logs system messages that are related to all HTTP connections.
    Foundation Logs system messages for core SAP Cloud Platform Mobile Services functionality.
    Hybrid Application Management Mobile Services cockpit or an API, and client interactions for requesting and downloading updated hybrid apps. Logs system messages that relate to managing hybrid apps.
    Offline Logs system messages that are related to the offline OData service.
    Proxy Logs system messages that are related to any client-back end interactions using SAP Cloud Platform Mobile Services as a proxy (for example, OData requests).
    Push Logs system messages that are related to push actions.
    Registration Logs system messages that are related to application registration.
    SAP Mobile Cards Logs system messages that are related to SAP Mobile Cards.
    Security Logs system messages that are related to security.
    Statistics Logs system messages that are related to usage statistics.

    Logging Levels

    Log Level Description
    Debug For debugging purposes, includes extensive and low-level information.
    Info Informational text, used mostly for echoing what has been performed.
    Warn The application can recover from the anomaly, and fulfill the task, but requires attention from the developer or operator.
    Error The application can recover from the error, but cannot fulfill the task due to the error.

Last update: August 12, 2020