View local logs-Mobile Platform as a Service(mPaaS)-阿里云帮助中心

The mPaaS log API writes logs to a local sandbox file first. The logs are then uploaded to the log server when the reporting logic is triggered.

Local log format

Versions 10.1.60 & 10.1.68

Local logs are stored in the Library > atrack > logs folder in the sandbox. This folder only contains unreported logs. Reported logs are deleted.
Log files are named BusinessCode.log. Logs are categorized by the business code (bizType) parameter passed during writing. Logs of the same type are written to the same file. Common instrumentation types:
- autotrack: Automatic instrumentation.
- behavior: Behavior instrumentation, such as app activation and custom event tracking. You can use the bizType parameter to define a custom business code. For more information, see Custom event instrumentation.
- performance: Performance instrumentation, such as app startup speed tracking.

Version 10.1.32

Important

As of June 28, 2020, mPaaS no longer maintains the 10.1.32 baseline. Use the 10.1.68 or 10.1.60 baseline series. For information about how to upgrade the baseline version, see the mPaaS 10.1.68 Upgrade Guide or mPaaS 10.1.60 Upgrade Guide.

Local logs are stored in the Library > log folder in the sandbox.
Log files are named BusinessCode.Timestamp.log. Logs are categorized by the business code (bizType) parameter passed during writing. Logs of the same type are written to the same file. Common instrumentation types:
- autotrack: Automatic instrumentation.
- behavior: Behavior instrumentation, such as app activation and custom event tracking. You can use the bizType parameter to define a custom business code. For more information, see Custom event instrumentation.
- crash: Crash instrumentation.
- performance: Performance instrumentation, such as app startup speed tracking.
A new .log file is generated each time the app performs a cold start.

Instrumentation log format

Log files are organized by line. Each line represents a single log entry.

Each log entry is a comma-separated string where the position of each value determines its meaning. A complete log entry has the following format:

0_     257_1479573031.408824_D-VM,2016-11-20 00:30:31:408,1000533192018_IOS-0000000001,2.0.X.X,2,-,7542B136-5EA8-4C3A-930D-8BF2CA15F3CA,-,event,-,-,-,-,-,-,startApp,-,u,c,Launcher,-,NativeApp,-,-,-,-,-,2,-,-,-,-,-,iPhone 6S,9.3.3,WIFI,-,-,follow_system_zh-Hans-CN,-,-,-,-,VoiceOver=0$$

In versions 10.1.60 and 10.1.68, the mark at the beginning of each log entry no longer indicates the log upload status.
In version 10.1.32, each log entry starts with a mark that indicates the upload status. 0 means the log has not been uploaded, and 1 means it has been uploaded.
For details about each log field, see Log model.

What to do next

Report logs