Logging

Logging

In cases where something went wrong at runtime, it’s helpful for integrating application to have as much information about failure as possible. CM SDK is using logs with data about various events, that should help programmers to reconstruct the sequence of events, to determine where problems occurred and to help with resolving these issues.

Log statements are divided info 5 levels (error, warning, info, debug, verbose) based on severity of contained message. Each statement also contains so called tag. Same value of tag is used for multiple related messages or source components. Content of CM SDK logs can be filtered based on tags, but beyond, it is not meant for any other advanced machine processing.

To provide better control over logging, CM SDK has an option to inject custom implementation of logging interface (see Initialization and config). This way, integrating application decides where those logs end up (e.g. logging to local console, custom library, or dedicated log file) and what logs actually get written (e.g based on log level or tag).

Continue to Threads