Overview

Logging and Log Upload are two critical aspects when considering large scale RDK deployment. STB stores logs for limited number of days (~10 days). Log repository get logs for a week or so which can help in debugging deployed STBs.

More details on how logging is done in RDK-V can be found here: RDK Logger

Importance of Logging in RDK Deployments

• Logs for deriving field matrices
• Logs for assessment of the criticality of the situation
  • Should I look at the problem at the middle of the night or can wait till next day morning
• Controlled log uploads from 100% to very small numbers (2-3%)based on device maturity
• Configurable upload intervals typically done once in a day
• Right level of abstraction to balance between the available storage space and the logs generated
• Rotate-backup-upload policies

RDK-V Log Upload Mechanism

Responsible for gathering local logs, packaging them, and uploading them to a remote URL. A client-side scheduler would control when it executes, but it could also be activated via immediate triggers from the log upload checker, SNMP MIBs, or other local actions.

The Uploader is responsible for sending STB log files to a remote file store. It performs the following:

• Responds to triggers (i.e. from cron or the SNMP agent)
• Checks local Device Settings for the URL of the file store, the logs it should send, and the repository it should use
• Gets connection credentials
• Makes a connection to the remote server and sends the files