Introduction

CPE has many metrics that are powerful for the analysis of trends and performance insights. Some sources of those metrics are applications or any of the RDK subsystems and TR-069 values. An easy way to get some application metrics is through the log strings they write to log files. The conventional way of accessing this content has been through the upload of these files to servers and then processing the data from them. However, this content has not been available to the range of operations engineers, analysts, managers, and others who want to search for and monitor issues. Moreover, the current response time is inadequate; a delay of 24 hours is excessive in many instances. To enhance timeliness, the 'Telemetry' component is created that enables devices to transmit specific metrics from designated logs and TR-069 at near-real-time intervals.

RDK Telemetry improved on the early practice where the RDK would simply bundle log files once a day and transfer the bundle to a file server. Both RDK-V and RDK-B devices provide telemetry with several key features: more real-time data, configurable metrics or events that the CPE should retrieve and send, improved upload frequency that made the timeliness of this data more relevant to analysts, more sources of metrics and events such as log files or TR-069 parameters, an improved cloud solution for analytics using big data solutions for receiving streams and storing data for reporting, and real-time metrics using terse key/value pairs (e.g., {"Report":[{"mac":"AA:BB:CC:DD:EE:FF"},{"TelemetryEnabled":"true"},{"CpuUsage":"48"},{"Uptime":"824"},{"FreeMem":"2036476"},{"TotalMem":"1212772"}]}.

Key Features

• Telemetry data transmission to servers at pre-defined intervals
• Leverages logs, different system status information.
• Uses key-value pairs for data upload.

Architecture

RDK telemetry data is sent periodically from every RDK device, with XConf sending certain parameters during bootup, specifying what parameters to gather and where to retrieve them from, such as logs or status information (e.g., CPU load, memory usage) using system commands. The CPE sends a request to the server with version and device details, and based on server rules, the telemetry agent retrieves telemetry markers from the server, gathers the required data from logs, and packages it into a JSON message. This message is then sent to a server where it is processed and updated in storage, with the server configuring how often it needs telemetry data.

How it works

The telemetry upload process is controlled through the dcm-log service

1. DCMscript.sh communicates with the XConf server and fetches the predefined markers
2. Using the markers, DCM Script will prepare a sorted map file for the log lookup and creates a DCA Agent cron job.
3. Cron job retrieves data from the device
4. From the retrieved data, it will create a JSON formatted message.
5. JSON format data will be uploaded to the server 

Telemetry using community XConf server

XConf server configuration procedure:

1. XConf Telemetry configuration starts with adding DCM settings as telemetry is a subset of log upload process in general, Below are the steps involved in DCM configuration:
   1. Add a Upload Repository – Tells Device about the server side file store where log files will be updated
   2. Add a Formula
   3. Map the configuration with a build condition (such as a MAC/IP/Model combination)
   4. Create Log Upload Settings (Tells devices when to upload the logs)
   5. Create Device settings (Tells when the device should reach XConf for a configuration polling)
2. Telemetry configuration can be done by adding a permanent profile which contains below objects
   1. Upload repository
   2. Profile options (Header, content, frequency etc.)
      1. The telemetry marker which is a combination of Header(for identification), Content(string to search in the log files), Type (name of the log file), and Polling frequency (after which iteration to send). Telemetry profile entries can be set depending on the target platform. I.e.RDK-B and RDK-V. Eg:header : mem_rmfStreamer, content : rmfStreamer, type : top_log.txt , and polling frequency : 60.
3. Creating a targeting rule which is basically mapping the profile to a set of MAC/IP/Device etc.

Refer Xconf Server - User guide for configuration and feature validation for detailed steps.

Client(device) side verification

1. Client side configuration which involves:
   1. SSH to RPI
   2. Change the configuration in /etc/dcm.properties
   3. Debug & check everything is good by restarting the log service and monitoring the log file

For detailed steps

on configuring the XConf server

and validating Telemetry 1.0 features on RDK-B and RDK-V platforms, including sample logs, please click

Video client side setup details are captured below:

# DCM properties file
# Log server details
LOG_SERVER=xconf.rdkcentral.com
# Log upload server details
DCM_LOG_SERVER=https://xconf.rdkcentral.com/xconf/logupload.php
DCM_LOG_SERVER_URL=https://xconf.rdkcentral.com:19092/loguploader/getT2Settings
# SCP server details
DCM_SCP_SERVER=xconf.rdkcentral.com
# LA server details
DCM_LA_SERVER_URL=https://xconf.rdkcentral.com/xconf/logupload.php

tr181 -s -t boolean -v true Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.Enable
tr181 -s -t string -v 2.0.1 Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.Version
tr181 -s -t string -v https://xconf.rdkcentral.com:19092/loguploader/getT2Settings Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.ConfigURL

here for RDK-B and here for RDK-V.