...

RDK supports following tools for making the debugging task easier for developers.

• rmfApp
• Breakpad
  
  

Logging

Presentation of system events, errors and application traces altogether in form of console messages or persistent log files constitutes the logging process in RDK.

Generating and reading system logs is an important aspect of system administration. The information in system logs can be used to detect hardware and software issues as well as application and system configuration errors. This information also plays an important role in assessing device health, security loopholes and incident response.

There are multiple levels of logging supported by RDK right from having the native Linux syslog (or more recently : journal logs) facility to having a dedicated logging facility such as RDK logger library.

RDK Logger

Description

Provides logging capability.

Capabilities

• Abstracts logging client from underlying logging utility.
• Dynamically enable/disable logging level at run time.
• Provide logging format that complies with the existing format understood across RDK components(e.g. <timestamp> [mod=*, level=*]).
  

Systemd Journals

systemd has its own logging system called the journal; therefore, running a syslog daemon is no longer required.
Journal stores all logs in a specified folder
journalctl allows you to filter the output as needed
In order to comply with the rdk logging formats, journalctl is used to redirect logs to specific module level log .txt files
The future plan is to switch to using journald systems-journal-upload to upload logs