Query Code Extension Logs by Using the Query API

Use the Data 360 Query API to programmatically retrieve logs generated for code extension runs. Logs are stored in the Data Lake Object (DLO) named DataCustomCodeLogs__dll. You can query them like any other DLO.

• Data 360 access with permission to query data
• Enable Code Extension in Data Cloud Setup by using the Feature Manager. See Enable Data 360 Features in Feature Manager.
• Authenticate to the Data 360 Connect API. See Get Started with Data 360 Connect API.
• A completed batch transform execution

• Latency: Logs typically appear within a few minutes after code execution. Allow up to about 10 minutes.
• Message limits: Maximum log message length is 31,072 characters. Longer messages are truncated.

1. Understand the relevant fields of the DataCustomCodeLogs__dll DLO.

   • EventId__c — DLO primary key for each log record
   • Timestamp__c — Log record timestamp
   • Message__c — Your log message
   • CorrelationId__c — Correlates your code extension logs to Data 360 internal logs
   • DataCustomCodeName__c — Name of the code extension package
   • ProcessDefinitionName__c — Name of the batch data transform that uses the code package
   • ExecutionId__c — Unique identifier for the code execution. More than one CorrelationId__c can share one execution
   • UsedInFeature__c — Feature where the code is used, for example, batch data transform
   • OrgId__c — Org identifier

2. Create your SQL query to query the DataCustomCodeLogs__dll DLO like any other Data 360 object. See Create sql query.

   Examples

   • Filter by transform (process) name.
   • Filter by code extension package name.
   • Filter by execution ID.
   • Filter by correlation ID.

3. Check the query status. See Get SQL Query Status.

4. (Optional) Retrieve additional rows. If your query returns more data than the initial response, retrieve additional rows. See getSqlQueryRows.

• Query Code Extension Logs by Using Query Editor