RDKB CcspLogAgent Component in RPI - Design - 2019 M7

Introduction

All components have separate TR181 parameters to control the  LogLevels  and  LoggerEnable  options during run-time.                                                                                                  

All components logger TR181 parameters exist in LogAgent.xml file which is handled by CcspLogAgent component. Those parameters are stored in syscfg.db file for persistent storage.

• LoggerEnable: This will help to enable/disable logs for particular component. If it is TRUE logs are enabled otherwise logs are disabled.

Note: We can enable/disable logging for the all components based on “X_RDKCENTRAL-COM_LoggerEnable” parameter. It is by default set to “TRUE”.

• LogLevels: We can set different log levels for each component. By default all modules log level is 4 (RDK_LOG_INFO).
  
  CcspLogAgent component provides the ability to change the log levels at run time for individual components.

Below mentioned are the supported LogLevels:

If LogLevel is set to 3, all logs related to 0 to 3 levels are routed to logger which means RDK_LOG_FATAL, RDK_LOG_ERROR, RDK_LOG_WARN and RDK_LOG_NOTICE prints are routed to logger, other prints not routed to logger.

Note: Log level for all components can be controlled using “X_RDKCENTRAL-COM_LogLevel” parameter. It is by default set to level 4 which is RDK_LOG_INFO.

RDK-B Logger Architecture

Example:

TR069 parameters for RDK logger,

Device.LogAgent.X_RDKCENTRAL-COM_TR69_LoggerEnable

Device.LogAgent.X_RDKCENTRAL-COM_TR69_LogLevel

PAM Parameters for RDK logger,

Device.LogAgent.X_RDKCENTRAL-COM_PAM_LoggerEnable

Device.LogAgent.X_RDKCENTRAL-COM_PAM_LogLevel