Introduction

While migrating to Telemetry2.0 from  DCA telemetry, the traditional log grepping is targetted to reduce as much as possible by instrumenting the  markers coming from RDKB components.To achieve this, RDKB components are supposed make required changes with the use of APIs from Telemetry 2.0 shared library.

RDKB Telemetry Components

1. Xconf Server
2. RPI with rdkb image

Environment Setup

2.1.  Build procedure

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

RDK-B R-Pi Yocto 3.1 - Dunfell

Note: Proceed the build procedure in Ubuntu18 version VM

2.2.  Pre- requisites for enabling Telemetry2_0

1. dmcli eRT setv Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.Enable bool true
2. dmcli eRT setv Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.Version string 2
3. dmcli eRT setv Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.ConfigURL string https://xconf.rdkcentral.com:9092/loguploader/getT2Settings
4. touch /nvram/enable_t2_debug
5. reboot the device
6. pidof "telemetry2_0"

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

$ systemctl disable rdkbLogMonitor

Below sample screenshots are enabling the T2 process  in target device(rpi),

After reboot the device,

Sample Successful logs for Telemetry 2 process Initialization,

 Xconf server

• Xconf server page :  https://xconf.rdkcentral.com:9093/admin/ux/

Configuring Telemetry on Xconf server

Change Application to stb in top right corner of the window

Create Formula

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

Create Device Settings

Xconf Server → DCM → Device Settings 

 Create Upload Repository

Xconf Server → DCM → Upload Repository

Upload Repository : HTTP Server

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

Create LogUpload Settings

Xconf Server → DCM → LogUpload Settings

Test Page

Xconf Server → DCM → Test Page

In the Test Page, give estbMacAddress(B8:27:EB:1B:56:4C → Mac Address of RPI) and ensure the parameters that has been configured in the DCM.

Create Permanent Profiles

The markers are of 3 types .
1.Split based markers. 
2. Count based markers
3. TR-181 based markers.

{"header":"RF_ERROR_IPV6PingFailed","content":"Ping to IPv6 Gateway Address are failed","type":"SelfHeal.txt.0","pollingFrequency":"0"}

{"header":"bootuptime_ClientConnectComplete_split","content":"Client_Connect_complete:","type":"LM.txt.log","pollingFrequency":"0"}

In T2.0,  the aim is to instrument possible number of split and count based markers from component side. These are termed as event markers. Can be classified as one more type under the classification of  markers.
Once a marker is instrumented from component side, its configuration on xconf will be changed  from the configured file name to "<event>" in   'type:' section.

Example: 

{"header":"bootuptime_ClientConnectComplete_split","content":"ccsp-lm-lite","type":<event>","pollingFrequency":"0"}

Xconf Server → Telemetry → Permanent Profiles

Create Targeting Rules

Xconf Server → Telemetry → Targeting Rules

Test Page

Xconf Server → Telemetry → Test page

In the Test Page, give estbMacAddress(B8:27:EB:1B:56:4C→ Mac Address of RPI) 

JSON Response

https://xconf.rdkcentral.com:9092/loguploader/getT2Settings?estbMacAddress=b8:27:eb:1b:56:4c&firmwareVersion=rdkb-generic-broadband-image_rdk-next_20210329055811&model=&partnerId=RDKM&accountId=&ecmMacAddress=B8:27:EB:1B:56:4C&env=dev&controllerId=2504&channelMapId=2345&vodId=15660&version=2

RAW data Response

RAW Data Response of T1

https://xconf.rdkcentral.com:9092/loguploader/getSettings?estbMacAddress=b8:27:eb:1b:56:4c&firmwareVersion=rdkb-generic-broadband-image_rdk-next_20210329055811&model=&partnerId=RDKM&accountId=&ecmMacAddress=B8:27:EB:1B:56:4C&env=dev&controllerId=2504&channelMapId=2345&vodId=15660&version=2

RPI(target) devices Response's

RPI device Logs

Successful communication logs between device and xconf server,

In T2, Receiving events from RDKB components  and comparing those events in Uploaded Makers list in xconf,

JSON Report

Successful logs for sending the JSON report to xconf server,

 Configuration file

• Once the profile details are successfully retrieved , the conf file will be created under /nvram/.t2persistentfolder/DCMresponse.txt which has the server configurations 

Log File

$ cat /rdklogs/logs/telemetry2_0.txt.0

$ cat /rdklogs/logs/dcmscript.log

Log upload onto HTTP Server

Verify that Json file  displayed in HTTP server → https://35.161.239.220/xconf/upload/

JSON file upload

• open the uploaded json file and ensure the parameters

https://35.161.239.220/xconf/upload/b827eb1b564c_TELE_05-26-2021-07-45AM.json