Client-side diagnostic log flags

LogDataChangeEvents

Logs each data change event, including error events.

LogDeadlocks

Logs each deadlock retry. Errors resulting from exceeding the retry count are always logged.

LogErrorXML

Logs the XML content for XML messages that fail.

LogEvtBrokerHeartbeat

Logs subscriptions, when subscriptions are canceled, when the heartbeat is refreshed, and when subscriptions are processed.

LogSequenceDetails

For a call being made from the client, logs the sequence key and sequence number of the message that is being processed asynchronously.

LogSyncCmdStats

Logs the overall execution time of synchronous commands, specifically the exit command, including the client ID and duration in milliseconds. It only logs entries if the execution time exceeds 50 milliseconds. The log flag applies to ExecCmd and GetDS calls.

LogSessionKeyInfo

Logs messages related to session key processing, including when session keys are read from ADS, checked for validity (every two minutes), and updated if expired. This helps track session key refresh events and ensures all running applications use the current session key.

LogSessionKeyRefreshInfo

Logs when a session key refresh occurs, specifically indicating that the session key information is being written to ADS after expiration. It records these events regardless of the time taken, ensuring visibility into session key refresh actions.

LogTokenClientInfo

Logs messages related to access token processing, including periodic checks (every 5 minutes) to verify if the current access token is valid or if a new one needs to be requested. This helps monitor token validity and renewal across running processes.

LogValidationError

For a call being made from the client, logs the message that was submitted if its validation fails when the synchronous or asynchronous command fails or when the event broker subscription fails.

Start-Stop

When this flag is turned on, the steps that are executed when connecting the client middleware proxy to the middleware are logged. The step log entries contain the context data at each step. The context data can help with diagnosing connection issues.

Note: It is strongly recommended to turn on this flag only for diagnostic purposes. This is because when this flag is on, several messages will be logged by the Logger every time that the client middleware proxy pings the middleware to verify that the connection is working.

Trace

Logs every XML message and its response as they go through the WCF Proxy. It also shows all EventBroker subscriptions and re-subscriptions.