Setting Up Device Logging Policy Parameters

To enable configured device logging policy, select the Policy is Active checkbox. If checkboxes are deselected on the Project Logging Policy and Global Logging Policy tabs, logs of the mobile device linked with this project are not written in the System Logs subsection.

To set up schedule of sending logging policy to a mobile device, set the parameters:

2. Hours/Minutes. Set the time of sending logging policy as follows: <hours : minutes> for the following ending period: In Specified Number of Hours (Minutes), Daily (UTC+0), On Specified Days of Month (UTC+0).

3. Execute. Select one of the logging policy sending periods:

• Never. Select the checkbox to disable scheduled sending of logging policy.

• In Specified Number of Hours (Minutes). Select the checkbox and set the repetition interval of sending logging policy as follows: <hours : minutes> in the Hours/Minutes box.

NOTE. The logging policy sending period starts after clicking the Save button.

• Daily (UTC+0). Select the checkbox and set the time of daily sending logging policy as follows: <hours : minutes> in the Hours/Minutes box taking into account the time zone UTC+0. The time zone used by the administrator does not affect the specified time.

• In Specified Days of Each Month (UTC+0). Select the checkbox and set the time of sending logs as follows: <hours : minutes> in the Hours/Minutes box and month days in the empty box taking into account the time zone UTC+0. The time zone used by the administrator does not affect the specified time.

TIP. When selecting the logging policy sending period, take into account the increase in mobile platform server loading and slowdown of mobile applications work if the frequent sending period is selected.

After executing the operations the logging policy is sent from mobile platform server to a mobile device by the specified schedule.

To set up schedule for sending logs from mobile device to server, set the parameters:

2. Hours/Minutes. Set time of sending logs as follows: <hours : minutes> for the following sending period options: In Specified Number of Hours (Minutes), Daily (UTC+0), In Specified Days of Each Month (UTC+0).

3. Execute. Select one of log sending periods:

• Never. Select the checkbox to disable log sending on schedule.

NOTE. To send logs manually from mobile device to server, use methods for working with logs.

• In Specified Number of Hours (Minutes). Select the checkbox and set the frequency of repeated log sending as follows: <hours : minutes> in the Hours/Minutes box.

NOTE. A log sending period counts after clicking the Save button.

• Daily (UTC+0). Select the checkbox and set the time of daily sending logs as follows: <hours : minutes> in the Hours/Minutes box taking into account the time zone UTC+0. The time zone used by the administrator does not affect the specified time.

• In Specified Days of Each Month (UTC+0). Select the checkbox and set the time of sending logs as follows: <hours : minutes> in the Hours/Minutes box and month days in the empty box taking into account the time zone UTC+0. The time zone used by the administrator does not affect the specified time.

TIP. When selecting the log sending time option take into account increase in mobile platform server loading and decrease of speed of mobile applications work when logs are sent too frequently.

After executing the operations, logs are sent from a mobile device to server by the specified schedule.

To set up mobile device logs, set the parameters:

2. Logging Level. Select the system events logging level in the drop-down list:

• DEBUG (debug info). Log all debug events.

• INFO (analytical information). Default value. Logging of errors, warnings, messages, and getting statistical data about method work of the Android and JVM frameworks 25.03:001 or later. After framework methods are executed, the file analytics_<user name>_<device identifier>_<file send timestamp>.txt is saved to local storage (the analytics directory) of corresponding project on mobile platform server. The example of file name: analytics_user_616c07cedc50ec36_1748950212854.txt.

File contents:

{
    "timestamp": "1743679529206", // timestamp | mandatory parameter
    "device_id": "616c07cedc50ec36", // device identifier | mandatory parameter
    "login": "user", // user name | mandatory parameter
    "level": "info", // system event logging level | mandatory parameter
    "device": "Device", // mobile device model | mandatory parameter
    "fmp_ver": "25.03.01", // framework version | mandatory parameter
    "os_ver": "Android 12", // operating system and its version | mandatory parameter
    "method": "FMPDatabaseV1.select", // framework method | mandatory parameter
    "runtime": "8", // method execution time in milliseconds | mandatory parameter
    "request_id": "request_id", // request identifier | optional parameter
    "upload_vol": "2048", // volume of sent data from mobile device to mobile platform server in bytes | optional parameter
    "upload_time": "234", // time of loading data from mobile device to mobile platform server in milliseconds | optional parameter
    "download_vol": "2048", // volume of loaded data from mobile platform server to mobile device in bytes | optional parameter
    "download_time": "234", // time of loading data from mobile platform server to mobile device in milliseconds | optional parameter
    "measured_time": "123", // time of response from mobile platform server in milliseconds when executing the status method to check server availability during user authentication | optional parameter
    "await_time": "124", // time of response from mobile platform server in milliseconds | optional parameter
    "handle_time": "236", // time of data processing after loading to framework in milliseconds | optional parameter
    "params": // parameters of called method | mandatory parameter
    {
        "query": "SELECT * FROM getUser_armso_userParams"
    }
}

• WARN (information about events that may cause errors). Log errors and warnings.

• ERROR (error information). Log errors.

2. Write Sensitive Information to Logs. Select the checkbox to save cache data to logs if required. The checkbox is deselected by default.

IMPORTANT. Writing of cache data to logs may affect system security.

2. Send Syslog from Device. Select the checkbox to send mobile device's syslog logs to mobile platform server. Logs meet requirements of the RFC 5424 standard and are sent to server as a syslog file that is saved to local storage of corresponding project.

NOTE. Sending the syslog file from mobile device to mobile platform server is available in the Android framework 25.03:002 or later.

2. Where to Load Logs on Device. Select the location on a mobile device where to load logs:

• Database. Default value.

• System Log.

• Database and System Log.

TIP. It is recommended to load logs to the system log during application debugging.

2. Database Weight, at which Logs are Loaded (Mb). Specify database size in megabytes, at which logs will be loaded to mobile platform server. 10 Mb is used by default.

2. Maximum Database Weight (Mb). Specify the maximum database size in megabytes, at which new logs will overwrite old ones for optimal use of mobile device resources. 10 Mb is used by default.

After executing the operations, mobile device logs are set up.