...

Why we need notifications?

• To ensure whether that the value is set properly and updated in the database.

Module and component

• Logging mechanism - Mechanism: RDKB Logger
  The RDKB logger is linked to RDK-B modules to enable component-wise logging.
• Component responsible Responsible for enabling/disabling notifications: Enabling/Disabling Notifications
  • By default, the system will look for /etc/debug.ini.
  • rdklogctrl can be used in runtime at runtime.

During Boot-up 

• When the RPi boots up, each RDK-B component will be initialized, which in turn will initialize the logger and start logging into the corresponding log file, depending on the log level set for the component in /etc/debug.ini

How enable/disable notifications works?

• The notifications Notifications are enabled by default, and the levels can be referred to in /etc/debug.ini.
• Using rdklogctrl, we can disable the logs from any module which is integrated with rdklogger

Notification levels 

• Files :
  1. ./etc/debug.ini
  2. rdkb_log4crc configuration files
  Level for all components can be controlled using “X_RDKCENTRAL-COM_LogLevel”
  1. rdklogctrl <app_name> <module_name> <loglevel>
     rdklogctrl CcspWifiSsp LOG.RDK.WIFI FATAL,ERROR,WARN,NOTICE,INFO,DEBUG,TRACE1-TRACE9
• The default log level levels set toe for components are FATAL,ERROR,WARN,NOTICE,INFO.
• Log levels can be controlled independently for each module.

Examples

Changing SSID name

...