Administrator

Setting Log Levels

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

Context

Logging detailed information consumes more 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, logging errors and warnings is sufficient.

Procedure

  1. In Management Cockpit, select Start of the navigation path Logs Next navigation step Log Settings End of the navigation path.
  2. For each component, select a log level.
    Table 22: System Logging Components
    Component Description
    Admin Logs system messages related to SAP Mobile Platform administration.
    Agentry Logs system message related to Agentry applications.
    Agentry user.* Logs system messages related to Agentry application users.
    Agentry <app_ID> Logs system messages related to the Agentry application.
    Agentry <app_ID>.BackEnd.* Logs system messages related to the back-end data source connections, such as SQL or Java, for the Agentry application.
    Agentry <app_ID>.ThirdPartyPushServices Logs system messages related to the back-end data source push service for the Agentry application.
    Agentry <app_ID>.WebSockets Logs system messages related to server/client communication using WebSockets connection type for the Agentry application.
    Agentry <app_ID>.WebSockets.connection.* Logs system messages related to server/client communication using WebSockets connection type for the Agentry application.
    B2C Application Services Logs system messages related to the Business-to-Consumer services used for Mobiliser logs. Mobiliser must be enabled to set log levels.
    B2C Framework Logs system messages related to the Business-to-Consumer framework used for Mobiliser logs. Mobiliser must be enabled to set log levels.
    Backend Request Header Trace

    When the logging level is set to Debug, logs the backend request and response headers issued by SAP Mobile Platform. This log can be used to analyze communication issues between SAP Mobile Platform and back end systems, including push services.

    Backend Request Wire Trace

    When the logging level is set to Debug, logs the backend request and response headers issued by SAP Mobile Platform, including the payload information (in binary or compressed format). This log can be used to analyze communication issues between SAP Mobile Platform and back end systems, including push services.

    Client Request Trace When the logging level is set to Debug, logs the client request and response headers issued by SAP Mobile Platform. This log can be used to analyze communication issues between SAP Mobile Platform and clients.
    Cluster Logs system message related to managing the cluster.
    Connectivity Logs system messages related to all HTTP connections made by the server.
    Foundation Logs system messages for core SAP Mobile Platform Server functionality.
    Hybrid Application Management Logs system messages related to managing hybrid apps through Management Cockpit or the API, and client interactions for requesting and downloading updated hybrid apps.
    Integration Gateway Logs server-side system messages for plug-ins integrated with SAP Mobile Platform Server, such as data sources (SAP and OData), and third-party systems and protocols (such as SOAP, JDBC, HANA Cloud, and NetWeaver PI).
    Offline Logs system messages related to the offline OData service.
    Other Controls all other loggers not covered here. This is implemented by having a single logger named ROOT in this component, setting the level of the root logger affects any logger that does not fall under one of the loggers have been assigned a level explicitly
    Proxy Logs system messages related to any client-back end interactions using SAP Mobile Platform Server as a proxy (for example, OData requests).
    Push Logs system messages related to push actions.
    Registration Logs system messages related to application registration.
    Security Logs system messages related to SAP Mobile Platform security.
    Serviceability Logs system messages related to framework components such a security or Web services, plus messages that are related to JDK and the server's runtime environment.
    Statistics Logs system messages related to usage statistics.
    Table 23: Logging Levels
    Log Level Description
    Path For tracing execution flow. Used, for example, in the context of entering and leaving a method, looping, and branching operations. (Not applicable to the offline logging component.)
    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.
    Fatal The application cannot recover from the error, and the severe situation causes fatal termination.