# Access logs with DLT

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

To enable DLT logging, users must set ENABLE\_DLT\_LOGGING in the build
            server:

    cd telaf
    
    export ENABLE_DLT_LOGGING=1
    source set_af_env.sh sa525m
    build-distclean-af; build-sa525m-afCopy to clipboard

Note: Once DLT logging is enabled, the crash log file will not be generated in
                /tmp/telaf\_crash\_logs or
                /data/telaf\_crash\_logs when a TelAF process crashes.

TelAF will assign a unique app ID for each service/app process based on the process name
            with the same context ID **TAFC**. The user can run the `dlt-control -j -u |
                grep APID` command to list all registered app IDs in DLT-daemon as
            follows:

    ~ # dlt-control -j -u | grep APID
    APID:37hR tafSMSSvc
    APID:51kj serviceDirectory
    APID:8pSY tafPMSvc
    APID:9ccx configTree
    APID:BT0p deviceManager
    APID:CD-- cv2x-daemon
    APID:EXkS tafVoiceCallSvc
    APID:E_vn tafECallSvc
    APID:EerR tafLocationSvc
    APID:Ft6s tafSomeipGWSvc
    APID:HxSc tafRpcProxy
    APID:I3YW tafDiagSvc
    APID:JMUK tafImuSensorSvc
    APID:LAag tafAudioSvc
    APID:LOGD logd -> dlt adapter
    APID:LaRF tafSimCardSvc
    APID:NVHi tafTimeSvc
    APID:OPsa tafCanSvc
    APID:RILD rild
    APID:SYS- DLT System Manager
    APID:TCS- telux_config_server
    APID:THRO throttleman
    APID:TTS- telux_thermal_server
    APID:Wo2p tafDataCallSvc
    APID:XGop tafNetSvc
    APID:YtfB tafFSCryptSvc
    APID:aIIo tafMRCSvc
    APID:bWMm watchdog
    APID:c9AG tafKeyStoreSvc
    APID:cMv5 tafHMSvc
    APID:cYZk tafGpioSvc
    APID:d5KE logCtrlDaemon
    APID:eVPj updateDaemon
    APID:iSHU tafDevInfoSvc
    APID:jTez tafUpdateSvc
    APID:jWXk tafRadioSvc
    APID:jk3Q tafThermSvc
    APID:k6_K tafVerInfoSvc
    APID:tv_4 supervisorCopy to clipboard

Users can set a TelAF application's own app ID and context ID through the process
            environments TAF\_DLT\_APP\_ID and TAF\_DLT\_CTX\_ID in
            the .adef file to override the default values if needed:

    processes:
    {
        envVars:
        {
            TAF_DLT_APP_ID = app1
            TAF_DLT_CTX_ID = ctx1
        }
        ...
    }Copy to clipboard

## DLT log level syncing

DLT has its own log level control that's different from Legato log level control. To
                make it easier for remote troubleshooting, TelAF automatically performs DLT to LE
                log level syncing. This means that if the DLT log level of ContextID (TAFC) for the
                calling TelAF process is changed by DLT-daemon, the LE log level of all LE
                components will be also updated based on the log level mapping rule.

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

**Parent Topic:** [Logging](https://docs.qualcomm.com/doc/80-41102-3/topic/logging.html)

Last Published: Apr 23, 2025

[Previous Topic
Access logs with syslogd](https://docs.qualcomm.com/bundle/publicresource/80-41102-3/topics/access-logs-with-syslogd.md) [Next Topic
Access TelSDK logs](https://docs.qualcomm.com/bundle/publicresource/80-41102-3/topics/access-telsdk-logs.md)