Introduction

Telemetry is the automatic recording and transmission of data from remote or inaccessible sources to an IT system in a different location for monitoring and analysis. A cron utility is used to schedule the Telemetry feature with a configured frequency and / or configured date and time.

Environment Setup

Build procedure

Follow the wiki page to make yocto's RDK-B image from yocto workspace in your PC.

Wifi-Extender Yocto Build Instructions

Note: Proceed the build procedure in Ubuntu18 version VM

Image Flash procedure

Refer the below link for image flashing

Turris Omnia Reference Platform: Flashing Instruction

 Xconf server

• Xconf server page :  http://35.155.171.121:9093/admin/ux/

Configuring Telemetry on Xconf server

Change Application to stb in top right corner of the window

     Image Added

Create Formula

 Login to Xconf Server and go to DCM menu item and click on “Formulas” sub menu and create Formula

Image Added

Create Device Settings

Xconf Server → DCM → Device Settings 

Image Added

Create LogUpload Settings

Xconf Server → DCM → LogUpload Settings

Image Added

Create Upload Repository

TFTP Server

Xconf Server → DCM → Upload Repository

Upload Repository : TFTP Server

Repository URL:  35.155.171.121

Image Added

HTTP Server

Xconf Server → DCM → Upload Repository

Upload Repository : HTTP Server

Repository URL:  http://35.155.171.121/xconf/logupload.php

Image Added

Create Permanent Profiles

Xconf Server → Telemetry → Permanent Profiles

TFTP Server

Upload Repository : TFTP Server

Repository URL:  35.155.171.121

Image Added

HTTP Server

Upload Repository : HTTP Server

Repository URL: http://35.155.171.121/xconf/telemetry_upload.php

Image Added

Create Targeting Rules

Xconf Server → Telemetry → Targeting Rules

Image Added

JSON Response

http://35.155.171.121:9092/loguploader/getSettings?estbMacAddress=D8:58:D7:00:A5:D6&model=Turris

TFTP Server

Image Added

HTTP Server

Image Added

Configuring Telemetry on Turris Omnia

• Once the board is up , go to /etc/dcm.properties and check for the below detail

DCM_LOG_SERVER_URL=http://35.155.171.121:9092/loguploader/getSettings
DCM_HTTP_SERVER_URL=http://35.155.171.121/xconf/telemetry_upload.php
DCM_LA_SERVER_URL=http://35.155.171.121/xconf/logupload.php

And in /etc/device.properties, ensure the model-name (provide a unique model name for the device) and the Tftp Server IP

MODEL_NAME=Turris

TFTP_SERVER_IP=35.155.171.121

• After board boot up, disable log rotation by using the command: 

$ systemctl disable rdkbLogMonitor

Important Note:

Disabling log monitor is required because log rotation feature will wipe out logs when threshold reached, due to which telemetry feature can't able to identify the event count. Telemetry functionality  requires rdk logs.

Steps to be followed:

1. Restart the dcm-log service using “systemctl restart dcm-log”
2. To check the status of the service “systemctl status dcm-log”
3. By triggering the service , Turris-Omnia starts uploading the logs and json file to the HTTP/TFTP server on the scheduled interval
4. The log upload and Telemetry markers can be uploaded via HTTP and TFTP as required
5. The profile can be verified using curl, conf file , through logs and in server.

Log Upload

• Both TFTP and the HTTP Logs and Json Upload will be into http://35.155.171.121/xconf/upload/