Query Code Extension Logs by Using Query Editor

Use Query Editor in Data 360 to view logs generated for code extension runs. Logs are stored in the Data Lake Object (DLO) named DataCustomCodeLogs__dll, and you can query them like any other DLO.

You can also use Data Explorer to view code extension logs saved in the DLO named DataCustomCodeLogs__dll. See View Your Data in Data Explorer.

Edition Table
Available in: Developer, Enterprise, Performance, and Unlimited Editions. See Data 360 edition availability.
User Permissions Needed
To query code extension logs by using Query Editor:Permission set:
  • Data Cloud Architect
  • Data 360 access and permission to use Query Editor in your org
  • Enable Code Extension in Data Cloud Setup by using the Feature Manager. See Enable Data 360 Features in Feature Manager.
  • A completed batch transform execution
  • Latency: Logs typically appear within a few minutes after code execution. Allow up to about 10 minutes.
  • Message limits: The maximum log message length is 31,072 characters. Longer messages are truncated.
  1. In Data 360, go to Query Editor.
  2. Select a workspace or create one. The workspace defines the objects and metadata that the query can access.
  3. In the left pane, click Data Lake Objects.
  4. Use the search box to find DataCustomCodeLogs or scroll through the list to locate and select it.
  5. Review the DataCustomCodeLogs__dll table to understand the relevant fields.
Field (API Name)DescriptionData type
EventId__cDLO primary key for each log recordUUID
Timestamp__cLog record timestampDatetime
Message__cYour log messageText
CorrelationId__cCorrelates your code extension logs to Data 360 internal logsUUID
ExecutionId__cUnique identifier for the code execution; multiple CorrelationId__c can share one executionUUID
DataCustomCodeName__cCode extension package nameText
ProcessDefinitionName__cName of the batch data transform that uses the code packageText
UsedInFeature__cFeature where the code is used, for example, batch data transformText
OrgId__cOrg identifierText
  1. From the DataCustomCodeLogs DLO dropdown, select how to create the query.
  2. Build a query based on your requirement by using the relevant fields of the DataCustomCodeLogs DLO. The editor suggests fields as you build the query. For information on building a SQL query in Data 360, see Get Started with Data 360 SQL.
  3. Click Run Query to view the results. To keep the query for future reference, click Save.
  • Filter by transform (process) name.
  • Filter by code extension package name.
  • Filter by execution ID (exact run).
  • Filter logs from the last 60 minutes.