Debugging folder or file structure
- Last UpdatedJul 21, 2026
- 1 minute read
- PI System
- Adapter for OPC UA 1.6
- Adapters
Because the overall number and size of each request or response pair captured by debugging can be quite large, the debugging information is stored in a separate folder. Debugging folders and files are created in the logs folder as follows:
Windows:
%ProgramData%\OSIsoft\Adapters\{adapterType}\Logs\EgressDebugLogs\{endpointType}\{egressId}\{omfType}\{Ticks}-{Guid}-{Req/Res}.txt
Linux:
/usr/share/OSIsoft/Adapters/{adapterType}/Logs/EgressDebugLogs/{endpointType}/{egressId}/{omfType}/{Ticks}-{Guid}-{Req/Res}.txt
The specific elements of the file structure are defined in the following table.
|
Element |
Represents |
|---|---|
|
adapterType |
The type of the adapter, such as OpcUa, Modbus or MQTT. |
|
endpointType |
The type of egress endpoint: Data or Health. |
|
egressId |
The Id of egress endpoint specified in configuration. |
|
omfType |
The OMF message type: Type, Container, or Data. |
|
Ticks |
The time in milliseconds (tick count) for UTC DateTime when the determined message was written to disk. |
|
Guid |
The unique GUID for each request or response pair. |
|
Req/Res |
Whether the message was HTTP request or response. |