RDK Logger

RDK Logger is a common logging library which is based on MPEOS logging & it uses log4c for formatting and supports multiple log levels

Capabilities

• Abstracts logging client from underlying logging utility.
• Dynamically enables/disables logging level at run time.
• Provides logging format that complies with the existing OCAP format (e.g. <timestamp> [mod=*, level=*]).
• Controls log level independently for each component/module.
• Enables logging globally via single configuration value.
• Controls initial log level for each component/module from configuration file (debug.ini) at startup.
• Prints formatted data to stdout.
• Separates logs into separate files based on "SEPARATE.LOGFILE.SUPPORT" configuration variable

RDK Logging architecture

Initialization

•  rdk_logger_init() loads entries from “debug.ini” and initializes log4c.
•  Sets log level of the module corresponding to environment variables.
•  Sets log level to default log levels, for the modules not having entries in configuration file. (Currently it is set as LOG.RDK.DEFAULT = ERROR in debug.ini)

Logging Configuration

Default level of logging is ERROR. But Logging settings are configured in debug.ini

LOG.RDK.<component1> = FATAL ERROR WARNING NOTICE INFO

LOG.RDK.<component2> = FATAL ERROR WARNING NOTICE INFO DEBUG

How to add the RDK logger functionality to the new module?

Include rdk_debug.h header file and make use of RDK_LOG for printing logs. Initialize RDK Logger by calling rdk_logger_init() in the respective module/component. Build new module/component by linking "librdkloggers.so" along with "liblog4c.so" and "libglib-2.0.so" shared object.

Example: -lrdkloggers -L ../opensource/lib -llog4c -lglib-2.0

RDK Logger Usage

RDK_LOG (rdk_LogLevel level, const char *module, const char *format,...)

• "level" is Log level of the log message (FATAL, ERROR etc). Apart from this there are special log levels like ALL, NONE, TRACE, !TRACE are supported.
• "module" is the Module to which this message belongs to (Use module name same as mentioned in debug.ini)
• "format" is a printf style string containing the log message.

All the RDK components logs are stored under /opt/log/ with a naming convention <RDK component>="">_log.txt.
For example, /opt/log/pod_log.txt includes all events logged by POD Manager module.

Sample code for Logging

For example, add a debug messages for "INBSI" module

RDK_LOG (RDK_LOG_NOTICE, "LOG.RDK.INBSI","<%s: %s>: Sending PMT_ACQUIRED event\n", PSIMODULE, __FUNCTION__);

User needs to provide the module name "LOG.RDK.INBSI", which is the same as mentioned in debug.ini

$ cat debug.ini
EnableMPELog = TRUE
LOG.RDK.INBSI = ALL FATAL ERROR WARNING NOTICE INFO DEBUG

Sample logging output

131011-21:21:49.578394 [mod=INBSI, lvl=NOTICE] [tid=4141] <SITP_PSI: NotifyTableChanged>: Sending PMT_ACQUIRED event

In this way, user make use of the RDK logger in the respective modules and control the logging levels through configuration file. Here, No need to build RDK logger again for the addition of new components/module.

How to use GStreamer logging

A callback function gst_debug_add_log_function() is registered to receive GStreamer logs. Logs are converted to RDK logs in callback function. RMF element which controls a gst-element shall register element name and corresponding log module using

void RMF_registerGstElementDbgModule(char *gst_module, char *rmf_module)

Callback function uses this information to get module names corresponding to gstreamer logs.

Logging Levels supported by RDK Logger

RDK Logging Configuration

RDK Logging Configuration

Default level for RDK logging is ERROR and logging settings are configured in debug.ini

LOG.RDK.<component1> = FATAL ERROR WARNING NOTICE INFO
LOG.RDK.<component2> = FATAL ERROR WARNING NOTICE INFO DEBUG

For Example:

LOG.RDK.UI = NONE
LOG.RDK.QAMSRC = ALL FATAL ERROR
LOG.RDK.VODSRC = ALL FATAL ERROR WARNING NOTICE INFO
LOG.RDK.MS = ALL FATAL ERROR WARNING INFO
LOG.RDK.GSTQAM = ALL FATAL ERROR WARNING INFO
LOG.RDK.IPPV = ALL FATAL ERROR WARNING NOTICE INFO
LOG.RDK.RMFBASE = FATAL ERROR WARNING INFO
LOG.RDK.TRM = ALL FATAL ERROR WARNING NOTICE INFO

How log files are uploaded to server

OCAP RI Logs

By default, stdout is redirected to /opt/logs/ocapri_log.txt for OCAP RI related logs.

Used By

All RDK Components

Uses

IARM

log4c

Used in Features

All

Interfaces

link to SVN or published/generated documentation

Owner

Hong Li

Code

Current Version - none

Change History - none

Known issues - none