Viewing Event Logs¶
Use event log information to troubleshoot application problems. Use search criteria to find specific log records and statements.
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.
You can enable detailed logging at the application level as described in Enabling Event Logs at the App Level. Note that detailed logging is used for troubleshooting, not for monitoring, so the log is reset after 24 hours. You can manually enable detailed logging again if you need more time for troubleshooting.
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. To enable detailed logging for applications, see Managing Apps. For the Cloud Build standalone service you can enable detailed event logging and default purge settings via Settings > 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 (using Enable Detailed Event Logging).
If you disable detailed logging, error logging is still done.
To view event logs:
In SAP mobile service cockpit, select Analytics > Logs.
(Optional) You can narrow the focus of event logs to view by setting filters such as Application ID, logging Level, Correlation ID, Feature Name, Time Frame (UTC+0000) (either a predefined time frame, or a custom time frame using the calendar date-picker to define a range), and User Name; and selecting Go. Select Reset Filter to clear your filter entries.
To view event log messages for a specific level, select Level, then select the logging level. Leave blank to include all 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 specific components, select Feature Name, then select the service names (or leave blank to include all services). Select Go.
System Logging Service Names
Service Name Description Mobile App Catalog Logs system messages that are related to managing the app catalog. Mobile App Update Logs messages that are related to application versioning services. Mobile Application Logs messages that are related to Native/Hybrid applications. Mobile Client Log Upload Logs messages that are related to uploading client application log files for analysis on the server. Mobile Client Resources Logs messages that are related to resources that can be accessed from mobile applications. Mobile Client Usage and User Feedback Logs messages that are related to uploading client usage and user feedback data for analysis on the server. Mobile Cloud Build Logs system messages that are related to the cloud build service. Mobile Cockpit Logs system messages that are related to SAP Mobile Services administration. Mobile Discovery Logs messages that are related to discovery services. Mobile Micro App Logs messages that are related to micro applications. Mobile Network Trace Logs messages that are related to network trace. Mobile Offline Access Logs system messages that are related to offline access to data on the mobile device. Mobile Push Notification Logs system messages that are related to native push actions for iOS and Android devices. Mobile Sample OData ESPM Logs system messages that are related to the OData sample service, which can be used during development and testing. Mobile Setting Exchange Logs system messages that are related to device registration and the exchange general settings between mobile client and server. mobile transaction bridge OData Logs system messages that are related to mobile transaction bridge processes. mobile transaction bridge Storage Logs system messages that are related to mobile transaction bridge storage.
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. Service Name Lists services 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.
(Optional) To download a text version of the event log file to the
Downloadsdirectory, select one or more rows, and click the Download icon.
(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. Multiple event messages, with a range of Seconds Before (-) After (+) values indicate that there are several correlated events. Use the values to establish the timeline of what happened leading up to and after the event.
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 event.
Level The logging level set for the component. Feature Name The component reporting the event. Message The message reported.
Enabling Event Logs at the App Level¶
For apps that have been migrated to the single-service model, you can enable detailed event logging at the application level.
You can specify the services to include, as well as Mobile AppRouter. This gives you more control over the event log information you want to see at the app level.
Detailed logging is used for troubleshooting, not for monitoring, so the log is reset after 24 hours. You can manually enable detailed logging again if you need more time for troubleshooting.
For applications that have not been migrated to the single-service model, you must enable detailed event logs at the service level. You still view the event logs for the application as described in Viewing Event Logs.
To enable event logs at the application level:
In SAP mobile service cockpit, select Mobile Applications > Native/Hybrid (or Mobile Applications > SAP Mobile Cards or Mobile Applications > Micro App).
Select an application, then select the Log Settings tab. Under Settings, all features that are assigned to the application appear. (If Log Settings does not appear, it means the app has not been migrated to the single service model).
Settings Description Feature Name All features that are assigned to the application appear, as well as the additional feature, Mobile AppRouter. Detailed Event Log Status Whether detailed event logging has been enabled for the feature at the app level.
In Edit Detailed Event Log Settings, select the features to include in event reporting for the application. Only features assigned to the app are available, plus Mobile AppRouter.
Click OK to save. Under Settings you can see the selected feature.