Skip to content

Viewing Event Logs

Use event log information to troubleshoot application problems. Use search criteria to find specific log records and statements. Depending on what information is captured, log information can include entries from event logs.

Context

Typically, one event log is captured per business operation. However for complex business processes, such as those for Offline and SAP Mobile Cards, data is collected throughout an operation, and written along with the general event log message. The multiple messages are associated using the Correlation ID, and provide you with more detailed information to better isolate a problem. One limitation is that the detailed messages aren't localized, that is, they're available only in English.

For some services, you can enable or disable detailed logging either at the application or settings level. In these cases, when you disable detailed logging, error logging is still done. For example, you can enable detailed event logging for the Cloud Build standalone service via Settings > Cloud Build to start logging the initialization of default purge settings for cloud build. To see the detailed event log related to build process for the cloud build, you need to enable the detailed event log for cloud build feature at the application level (see Enable Detailed Event Logging).

Procedure

  1. In Mobile Services cockpit, select Analytics > Logs.
  2. Select Event Logs.
  3. (Optional) Enter log search criteria.

    • To view event logs for a specific application, enter values for one or more of the following optional filters:
      • Application ID
      • Level
      • Correlation ID
      • Component
      • Time Frame
      • User name

    and click Go, then select the application.

    • To view event log messages for a specific level, select Level, then select the logging level. Leave blank to include all levels.

      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.
    • To view event log messages for a specific component, select Component, then select the service names; to select all service names, leave this field blank. Select Go.

      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.
    • To limit the results within a time frame, select the time frame; or set the time manually by selecting Custom Defined, entering a date range, and selecting OK.

    • To view log messages for requests initiated by a specific user, enter a user name.

    Logging information is based on your search criteria.

    Column Description
    Time The time and date stamp of the log entry.
    Level Level value, typically ERROR or WARN or INFO or DEBUG.
    Component Lists components by name.
    User Name The name of the user associated with the application ID.
    Message The link to detailed log information associated with the execution request.
  4. (Optional) To download a text version of the event log file to the Downloads directory, select one or more rows, and click the Download icon.

  5. (Optional) To view event log messages , select a row, and click the icon. Under Event Log Details and Application and User Details view a summary of event-related information.

    Under Related Events the event message appears. If you see a single event message, with a Seconds Before (-) After (+) value of 0, there are no correlated events. If you see multiple event messages, with a range of Seconds Before (-) After (+) values, there are several correlated events. Use the values to establish the timeline of what happened leading up to and after the event.

    Related Events

Field Value
Seconds Before (-) After (+) Indicates when the message occurred:
  • - (minus) ‒ the message occurred before the reported event.
  • 0 ‒ the event.
  • + (plus) ‒ the message occurred after the reported even.
Level The logging level set for the component.
Component The component reporting the event.
Message The message reported.

Last update: August 12, 2020