# Access TelSDK logs

Source: [https://docs.qualcomm.com/doc/80-41102-3/topic/access-telsdk-logs.html](https://docs.qualcomm.com/doc/80-41102-3/topic/access-telsdk-logs.html)

Some TelAF services are built on top of the TelSDK library. The log level mapping between
            TelSDK log level and DLT log level is as follows:

| TelSDK log level | DLT log level |
| --- | --- |
| LEVEL\_PERF | DLT\_LOG\_FATAL |
| LEVEL\_ERROR | DLT\_LOG\_ERROR |
| LEVEL\_WARNING | DLT\_LOG\_WARN |
| LEVEL\_INFO | DLT\_LOG\_INFO |
| LEVEL\_DEBUG | DLT\_LOG\_DEBUG |

To enable TelSDK DLT logging, users must create an additional
                telux\_<serviceName>.conf configuration file under the
            working directory for that TelAF service.

For example, to enable the TelSDK DLT logging for TelAF radio service, create a
                telux\_tafRadioSvc.conf file within
                /legato/systems/current/appsWriteable/tafRadioSvc/ with the
            following content:

    DLT_LOG_LEVEL=INFOCopy to clipboard

Then, after rebooting TelAF radio service, users can get both a TelAF log and TelSDK log
            for TelAF radio service with the same APPID.

**Parent Topic:** [Access logs with DLT](https://docs.qualcomm.com/doc/80-41102-3/topic/access-logs-with-dlt.html)

Last Published: Apr 23, 2025

[Previous Topic
Access logs with DLT](https://docs.qualcomm.com/bundle/publicresource/80-41102-3/topics/access-logs-with-dlt.md) [Next Topic
Logging tool](https://docs.qualcomm.com/bundle/publicresource/80-41102-3/topics/logging-tool.md)