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.
note: 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: <ul><li>Data Cloud Architect</li></ul> |
Prerequisites
- 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 or search index run
Considerations
- 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.
Steps to Query Code Extension Logs
- In Data 360, go to Query Editor.
- Select a workspace or create one. The workspace defines the objects and metadata that the query can access.
- In the left pane, click Data Lake Objects.
- Use the search box to find
DataCustomCodeLogs or scroll through the list to locate and select it.
- Review the
DataCustomCodeLogs__dll table to understand the relevant fields.
| Field (API Name) |
Description |
Data type |
EventId__c |
DLO primary key for each log record |
UUID |
Timestamp__c |
Log record timestamp |
Datetime |
Message__c |
Your log message |
Text |
CorrelationId__c |
Correlates your code extension logs to Data 360 internal logs |
UUID |
ExecutionId__c |
Unique identifier for the code execution; multiple CorrelationId__c can share one execution |
UUID |
DataCustomCodeName__c |
Code extension package name |
Text |
ProcessDefinitionName__c |
Name of the batch data transform or search index that uses the code package |
Text |
UsedInFeature__c |
Feature where the code is used, for example, batch data transform or search index |
Text |
OrgId__c |
Org identifier |
Text |
- From the
DataCustomCodeLogs DLO dropdown, select how to create the query.
- 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.
- Click Run Query to view the results. To keep the query for future reference, click Save.
Example Queries
- Filter by transform (process) name.
SELECT "EventId__c",
"Timestamp__c",
"Message__c",
"CorrelationId__c",
"ExecutionId__c",
"DataCustomCodeName__c",
"ProcessDefinitionName__c",
"UsedInFeature__c",
"OrgId__c"
FROM "DataCustomCodeLogs__dll"
WHERE "ProcessDefinitionName__c" = 'MyTransformName'
ORDER BY "Timestamp__c" DESC
LIMIT 100;
- Filter by code extension package name.
SELECT "EventId__c",
"Timestamp__c",
"Message__c",
"CorrelationId__c",
"ExecutionId__c",
"DataCustomCodeName__c",
"ProcessDefinitionName__c",
"UsedInFeature__c",
"OrgId__c"
FROM "DataCustomCodeLogs__dll"
WHERE "DataCustomCodeName__c" = 'my_custom_code'
ORDER BY "Timestamp__c" DESC
LIMIT 100;
- Filter by execution ID (exact run).
SELECT "EventId__c",
"Timestamp__c",
"Message__c",
"CorrelationId__c",
"ExecutionId__c",
"DataCustomCodeName__c",
"ProcessDefinitionName__c",
"UsedInFeature__c",
"OrgId__c"
FROM "DataCustomCodeLogs__dll"
WHERE "ExecutionId__c" = '00000000-0000-0000-0000-000000000000'
ORDER BY "Timestamp__c" DESC;
- Filter logs from the last 60 minutes.
SELECT "EventId__c",
"Timestamp__c",
"Message__c",
"CorrelationId__c",
"ExecutionId__c",
"DataCustomCodeName__c",
"ProcessDefinitionName__c",
"UsedInFeature__c",
"OrgId__c"
FROM "DataCustomCodeLogs__dll"
WHERE "Timestamp__c" >= TIMESTAMPADD('minute', -60, CURRENT_TIMESTAMP)
ORDER BY "Timestamp__c" DESC;
See Also