Versions Compared

Old Version 9

changes.mady.by.user Keerthana Pandurangan

Saved on

compared with

New Version 10

changes.mady.by.user Keerthana Pandurangan

Saved on

Key

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

...

$ systemctl disable rdkbLogMonitor

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

Image Added

After reboot the device,

Image Added

Sample Successful logs for Telemetry 2 process Initialization,

Image Added

 Xconf server

...

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>"

...

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

Curl Response


RPI(target) devices Response's

Successful communication logs between device and xconf server,

Image Added


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

Image Added

Successful logs for sending the JSON report to xconf server,

Image AddedExecute the following command in board, and ensure the output

 Configuration file

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

Image RemovedImage Added


Log File

$ cat /rdklogs/logs/telemetry.logImage Removed



$ cat /rdklogs/logs/dcmscript.log

Image Removed



$ cat /rdklogs/logs/dcmProcessing.logImage Removed



Log upload onto HTTP Server

Verify that Json file and zipped log files for all other logs file  displayed in HTTP server → httpserver → https://35.155161.171239.121220/xconf/upload/

JSON file upload

  • open the uploaded json file and ensure the parameters

...