Increase usage of DLT

DLT daemon (log collector) is running already and [some components|] use it. Audio manager is one of them actually.

The DLT viewer also works out of the box in the SDE, see here:

https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11573902#GDPSoftwareDevelopmentEnvironment(SDE)-ConnectingDiagnosticLogandTrace

So for the DLT area, the next action is to

• review which GDP components would benefit from logging
• review which GDP components are logging to other systems and consider changing them to DLT. (Notice however, proposed IVI-logging abstraction).

The purpose is to get more components to log to DLT so that when viewing the logs it gives an understanding of the whole running system.

It should be noted that individual component maintainers are given a lot of freedom in GENIVI to decide on their project content. With that said, here is what we will aim to achieve from GDP perspective:

• C++ code benefits from a C++ API. We therefore prefer ivi-logging class with DLT backend for C++ code. A secondary effect is that the base class API acts as an abstraction which enables modification to other logging systems if desired.

• For C code however, we do not make it a goal to put an abstraction over DLT if there is none already. In terms of the usage API it would only create something new with essentially the same function. (C-programs might still create some macros or functions to reduce repetition.)

AC

• Create an epic that can hold the work of porting components to use DLT
• Create a new story for each components that needs to be converted to use DLT for logging.