Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Children Display

Table of Contents

Telemetry 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.

RDKB Telemetry Components:

1. Xconf Server
2. Rpi Board with RDK Broadband image
3. Tftp Server

RDKB Telemetry Architecture:

draw.io Diagram
bordertrue
viewerToolbartrue
fitWindowfalse
diagramNameTelemetry Architecture - RPI
simpleViewerfalse
width
diagramWidth441
revision5

Rpi board will connect to Xconf Server to get the device configuration information, telemetry profile information and log upload repository (ip address of tftp server). It will search for the markers (contents mentioned in the permanent profile) in the mentioned log file. If it is found in the log file, it will process those information and create a text file and upload that file in the tftp server. This way all the critical data related to device health will be available on timely basis in the tftp server for further analysis.

XConf Server Configuration procedure:


1. Login to Xconf Server and go to DCM menu item and click on “Formulas” sub menu

...

19. Verify the created Targeting rule displayed on the Targeting rule page

RPi device side configuration and testing process:

Below steps needed after flashing for the first time:

...

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://35.155.171.121/xconf/upload)

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.

...