Versions Compared

Key

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

...

Logging Levels supported by RDK Logger

CodeDescription
RDK_LOG_FATALAny error that is forcing a shutdown of the service or application to prevent data loss (or further data loss), reserve these only for the most heinous errors and situations where there is guaranteed to have been data corruption or loss.
RDK_LOG_ERRORAny error which is fatal to the operation but not the service (cant open a file, missing data, etc)
RDK_LOG_WARNAnything that can potentially cause application oddities, but for which the application automatically recovering.
RDK_LOG_NOTICEAnything that largely superfluous for application-level logging.
RDK_LOG_INFOGenerally useful information to log (service start/stop, configuration assumptions, etc).
RDK_LOG_DEBUGInformation that is diagnostically helpful to people more than just developers.

RDK_LOG_TRACE1,

RDK_LOG_TRACE2,...

Only when it would be "tracing" the code and trying to find one part of a function specifically.

How to initialize RDK Logger

...

the script uploadSTBLogs.sh is responsible for uploading the logs to the server. Logs are uploaded as tar files with sufficient information like Mac ID, date , timestamp. Log can be uploaded to server using scp or tftp protocol as per server requirement.


API Documentation 

 To know more about SoC/Application level APIs details use in RDK, refer the link  RDK LOGGER API Documentation