All Products
Search
Document Center

View local logs

Last Updated: Jan 27, 2021
Important: Since June 28, 2020, mPaaS has stopped support for the baseline 10.1.32. Please use 10.1.68 or 10.1.60 instead. For how to upgrade the baseline from version 10.1.32 to 10.1.68 or 10.1.60, see mPaaS 10.1.68 upgrade guide or mPaaS 10.1.60 upgrade guide.

Logs generated by calling the log API are firstly stored in the local sandbox file, and then are uploaded to the log server when the upload logic is triggered.

Local log path

Version 10.1.68 & 10.1.68

  • Logs in the local sandbox are stored in the Library > atrack > logs directory, which only stores the unreported logs, and the reported logs are no longer stored.
    60 log path
  • Log files are named in the following format: Business code.log. Logs are classified based on the parameter bizType, and logs of the same type are stored in the same file. At present, the following common tracking types are available:
    • autotrack: Automation tracking.
    • behavior: Behavior tracking, including active state tracking and custom event tracking. You can define the business codes by the bizType parameter for custom event tracking. For more information, see Custom event tracking.
    • performance: Performance tracking, such as app startup time tracking.

Version 10.1.32

  • Logs in the local sandbox are stored in the Library/log directory.
    logLoc
  • Log files are named in the following format: Business code.Timestamp.log. Logs are classified based on the parameter bizType, and logs of the same type are stored in the same file. At present, the following common tracking types are available:
    • autotrack: Automation tracking.
    • behavior: Behavior tracking, including active state tracking and custom event tracking You can define the business codes by the bizType parameter for custom event tracking. For more information, see Custom event tracking.
    • crash: Exception tracking.
    • performance: Performance tracking, such as app startup time tracking.
  • A log file with the file name extension .log is generated upon each cold startup of an App.

Tracking log format

  • A log file consists of many logs, with one log in a row.
  • Each log contains several character strings separated by commas, with different meanings at different locations. The log server splits a log based on location information. The format of a complete log is as follows:
       
    1. 0_ 257_1479573031.408824_D-VM,2016-11-20 00:30:31:408,1000533192018_IOS-0000000001,2.0.0.0,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 version 10.1.60 & 10.1.68, the tag at the begining of each log no longer marks the upload status of log.
  • In version 10.1.32, each log contains a tag at the beginning. The first digit indicates the log upload status. Digit 0 indicates that the log is not uploaded. Digit 1 indicates that the log has been uploaded.
  • For the specific meaning of each field, see Log model.

What to do next

Upload logs