The "auditCode":"nodeContainerInfo" log event contains information about which system processes are used to run nodes.
It provides you with the ability to determine the container execution mode and PID of a running node.
Nodes can run in their own process space or 'in-container' within a shared process space, or they can run in their own exclusive process space.
Below is an example of the nodeContainerInfo event that is generated when a Transform node is run 'in-container' (which is the default for the Transform node when the system determines it is eligible to run within the node container).
{"timestamp":"2025-04-01T11:47:21.29471-04:00","auditCode":"nodeContainerInfo","userId":"5e0b418e-05e2-4a78-b969-fa15d5b8bd5b","username":"Adrian","tenantName":"defaultTenant","success":true,"arguments":{"node":"Audit_Log_containerInfo_Tests.Transform_In_Container","containerVersion":"1","containmentMode":"shared","containerType":"nodeContainer","nodeLocator":"object:element:1ed40a32-84f5-4f11-98aa-8523efe1d2bd~child:48d9a0cc-7c74-4196-b660-cbfc88f4fa0e","dataflowLocator":"object:!tenant:defaultTenant~directory:__Root__~directory:__Users__~directory:ebe80ebd-1d49-4b79-b10f-095db52df8b7~graph:3acdfed7-4b33-4fce-81de-83283e752058","containerPid":"1141435","graph":"Audit_Log_containerInfo_Tests"}}
In contrast, here is an example of the nodeContainerInfo event that is generated when a Transform node is configured to not run within the node container.
{"timestamp":"2025-04-01T12:06:59.534159-04:00","auditCode":"nodeContainerInfo","userId":"5e0b418e-05e2-4a78-b969-fa15d5b8bd5b","username":"Adrian","tenantName":"defaultTenant","success":true,"arguments":{"node":"Audit_Log_containerInfo_Tests.Transform_Outside_Container","containerVersion":"1","containmentMode":"exclusive","containerType":"binary","nodeLocator":"object:element:1ed40a32-84f5-4f11-98aa-8523efe1d2bd~child:0034e3d2-86f0-450c-892a-7043252c0d58","dataflowLocator":"object:!tenant:defaultTenant~directory:__Root__~directory:__Users__~directory:ebe80ebd-1d49-4b79-b10f-095db52df8b7~graph:3acdfed7-4b33-4fce-81de-83283e752058","containerPid":"1142584","graph":"Audit_Log_containerInfo_Tests"}}
In the latter example, the containerPid value indicates the Process ID of the thread used to run the individual node. This can be useful in the situation where you can see there is a long-running system process and you want to identify which node this relates to within a running data flow or scheduled run.
------------------------------
Adrian Williams
Precisely Software Inc.
------------------------------
Original Message:
Sent: 03-28-2025 19:07
From: Toby Harkin
Subject: auditcode = nodeContainerInfo
Does anyone have any documentation on the auditcode nodeContainerInfo? it seems to be missing from the documnetation.
docs/dist/help/admin/audit-logging
There is a field in the log file called containerPid which I am hoping links back to an OS level PID? My goal here is to link CPU/Memory etc stats from the OS back to a node or process within Data360. It would be very useful to get a more accurate indicator of what nodes and processes are truely driving impact to my server.
Cheers,
Toby.
------------------------------
Toby Harkin
TELSTRA CORPORATION LIMITED
Sydney NSW
------------------------------