Debugging folder or file structure
- Last UpdatedAug 20, 2024
- 1 minute read
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:
%ProgramData%\OSIsoft\Adapters\<adapterType>\Logs\EgressDebugLogs\<endpointType>\
Under that the folders will be created based on this format:
<egressId>\<endpointType>\
The file name will be of the format:
<Ticks>-<componentId>-,requestIdGuid>-<transactionIdGuid>-<operationIdGuid>-<Request/Response>.txt
The specific elements of the file structure are defined in the following table.
|
Element |
Represents |
|---|---|
|
adapterType |
The type of the adapter: EventsToCONNECT, OpcUa, Modbus, MQTT, and so on. |
|
endpointType |
The type of egress endpoint: Data or Health. |
|
egressId |
The Id of egress endpoint specified in configuration. |
|
messageType |
The Message Type: AuthorizationTags, AssetTypes, Assets, Enumerations, ReferenceDataTypes, EventTypes, ReferenceData, or Events. |
|
Ticks |
The time in milliseconds (tick count) for UTC DateTime when the determined message was written to disk. |
|
requestIdGuid |
The unique request identifier GUID for each request or response pair. |
|
transactionIdGuid |
The unique transaction identifier GUID for each request or response pair. |
|
operationIdGuid |
The unique operation identifier GUID for each request or response pair. |
|
Request/Response |
Whether the message was HTTP request or response. |