The following is a list of all the properties that can be present in the logs.
In the case of MySQL logs all of these properties will be present in the table, whereas in the file logs they have to be specified in order to appear in said files.
•LkGuid
Unique code that identifies every LinkarServer operation. Each operation may generate multiple log entries. The "LkGuid" allows you can locate every entry pertaining to the same operation, aiding in troubleshooting. LinkarWS operations also generate an "LkGuid" that is shared with LinkarServer and keeps the operation identifiable in the logs. This allows you to maintain the traceability of operations run from LinkarWS through LinkarServer.
•EntryPointName
The name of the EntryPoint where the operation was launched.
•Method
Name of the operation type that LinkarServer launched (READ, SUBROUTINE, SELECT, etc...)
•RequestTimeStart
Timestamp at the moment the operation enters LinkarServer.
•QueueDuration
The time in milliseconds the operation spent in queue before processing.
•DbTimeStart
Timestamp at the moment the operation is transferred to the database.
•DbDuration
The time in milliseconds the operation process took in the database.
•ResponseDuration
The total time elapsed from the point the operation enters LinkarServer to the point a response is received from the database, in milliseconds.
•SessionID
For volatile operations this will show the word "VOLATILE". For persistent operations it will show the GUID that identifies the operations run in that session.
•LkUser
The LinkarServer user that launched the operation.
•Account
The data account from which the operation is launched.
•IdLineDB
The number that identifies the database line in which the operation is launched.
•Language
Languange code the LinkarServer clients use in the "CredentialConnection" property for volatile or persistent operations.
•FreeText
Free text field the LinkarServer clients can specify in the "CredentialOption" property for volatile or persistent operations.
•OriginIp
IP address from which the LinkarServer operation is launched.
•CustomVars
Optional variables that can be added in the "CredentialOption" property for volatile or persistent operations.
•GeneralOptions
General configuration options for LinkarServer.
•Options
Specific configuration options for each LinkarServer operation.
•InputData
Database input data for the LinkarServer operation.
•OutputData
Reponse data from the database for the LinkarServer operation.
•DbError
Error messages, if any, from the database during the processing of the LinkarServer operation.
•Level
Serilog's level for the log entry.
•Message
Text containing information about the LinkarServer operation (can be error messages, operation details, etc.)
•IdLineLK
The number that identifies the LinkarServer line in which the operation is launched.
•LkServerVersion
LinkarServer version.
•LkClientVersion
LinkarServer Client version.
•LkClientId
Identifier for the type of LinkarServer client.
•LkPluginRef
Reference code for the LinkarServer plugin, if any is being used.
•Category
Identifier for the category of the message (STATUS) or error (ERR_XXX) type generated by LinkarServer. Where XXX references whether the error is related to the database type (ERR_TERMINAL_CLIENT, ERR_QM_CLIENT, ERR_UNIOBJECTS_CLIENT, ERR_JBASE_CLIENT, ERR_D3MVSP, ERR_SOCKET_CLIENT), is a LinkarServer error (ERR_CMS_MANAGER) or is a different internal LinkarServer error (ERR_SERVER, ERR_USRVAL, ERR_PLUGINVAL, ERR_CFG_XML, ERR_BROKEN_LINE)
•ErrorCode
Internal code for LinkarServer errors.
•MoreInfo
Additional information that may be supplied in some cases.
•Exception
When an internal exception is captured this will show any related information.
•Timestamp
Timestamp for the moment the log data is sent to Serilog. Serilog receives the data that is to be stored in the logs but the final writing to the logs (file or MySQL logs) is processed in batches. This timestamp only represents the time Serilogs received the data, not the moment it is written in the logs.
•_ts
Timestamp for the moment the data is written in the logs (File or MySQL logs).
