You can analyze the contents of the audit log. A copy of the log can be read using the JSON Data node.
The audit log can be found in the logs directory within the site directory for the system. The site directory location for a Desktop instance can be found here:
%localappdata%\Data3SixtyAnalyze\site\logs
e.g. C:\Users\<username>\AppData\Local\Data3SixtyAnalyze\site\logs
The audit log records events for when a node starts to run and completes running, e.g.
You can analyze the contents of the audit log. A copy of the log can be read using the JSON Data node.
The audit log can be found in the logs directory within the site directory for the system. The site directory location for a Desktop instance can be found here:
%localappdata%\Data3SixtyAnalyze\site\logs
e.g. C:\Users\<username>\AppData\Local\Data3SixtyAnalyze\site\logs
The audit log records events for when a node starts to run and completes running, e.g.
The "nodeProcessing" event indicates a node started running. The "nodeProcessed" event indicates when a node stopped running. You will need to correlate the start and stop events for each node. The nodeLocator's object:element attribute identifies the node's id. If a node completed successfully it's runState will be "PASSED". Other attributes of the log events provide details of the particular data flow and node in the data flow.