Page History

...

RPi device side configuration and testing process:

Below steps needed after flashing for the first time:
1. Flash the Telemetry

...

image

...

and load it

...

on RPi board

...

2. After board boot up,

...

disable log rotation by using the command: systemctl disable rdkbLogMonitor

...

3. Verify the image version: cat /version.txt
4. Perform reboot: reboot -f

Below steps are to check telemetry log whenever box boots up ( after first time boot ) :
1. Verify tftp server is running and XConf DCM and Telemetry Permanent profile is configured properly (see Telemetry User manual for XConf side configuration for Telemetry)
2. After reboot, verify Telemetry log: cat /rdklogs/logs/telemetry.log
3. Verify that rtl_json.txt

...

and zipped log files for all other logs displayed in tftp server
4. Verify that rtl_json file and zipped log files for all other logs displayed in AWS(http) server(http://34.219.243.214:81/xconf/upload)

Note:

Disabling log monitor is required because log rotation feature will wipe out logs when threshold reaches due to which telemetry feature can't able to identify the event count, which requires log to bring both log rotation and telemetry feature at same time. User needs to increase the threshold size of log rotation max size . Please follow Log Rotation Support in RPI User manual - Broadband - 2019 M8 to change threshold size of log rotation.

...

Future Enhancement:

1. We are not considering the cron job time setting for log collection and upload.
2. We are not considering the polling frequency parameter in Telemetry profile entries section of Permanent profile page under Telemetry menu. As of now polling frequency value is considered as 0.

...