RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
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.
1. Xconf Server
2. RPI with rdkb image
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
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
Configuring Telemetry on Xconf server
Login to Xconf Server and go to DCM menu item and click on “Formulas” sub menu and create Formula
Xconf Server → DCM → Device Settings
Xconf Server → DCM → Upload Repository
Upload Repository : HTTP Server
Repository URL: http://35.161.239.220/xconf/telemetry_upload.php
Xconf Server → DCM → LogUpload Settings
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.
The markers are of 3 types .
1.Split based markers.
2. Count based markers
3. TR-181 based markers.
Marker Type | Sample configuration from xconf | Description with respect to sample configuration |
---|---|---|
Count based markers | {"header":"RF_ERROR_IPV6PingFailed","content":"Ping to IPv6 Gateway Address are failed","type":"SelfHeal.txt.0","pollingFrequency":"0"} | Expects the occurrence count of content "Ping to IPv6 Gateway Address are failed" |
Split based markers | {"header":"bootuptime_ClientConnectComplete_split","content":"Client_Connect_complete:","type":"LM.txt.log","pollingFrequency":"0"} | Expects the value after content "Client_Connect_complete:" |
TR-181 based markers | {"header" : "CMMAC_split","content" : "Device.DeviceInfo.X_COMCAST-COM_CM_MAC","type" : "<message_bus>","pollingFrequency":"48"} | Markers whose type is configured as "<message_bus>" |
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
Xconf Server → Telemetry → Targeting Rules
Xconf Server → Telemetry → Test page
In the Test Page, give estbMacAddress(B8:27:EB:1B:56:4C→ Mac Address of RPI)
Execute the following command in board, and ensure the output
$ cat /rdklogs/logs/telemetry.log
$ cat /rdklogs/logs/dcmscript.log
$ cat /rdklogs/logs/dcmProcessing.log
Verify that Json file and zipped log files for all other logs displayed in HTTP server → http://35.155.171.121/xconf/upload/
http://35.155.171.121/xconf/upload/D858D700A5D6_TELE_11-30-2020-12-31PM.json
Ensure all the log files present in the zipped file