Message Tracing

For debugging and development purposes, the persistence service can trace individual messages as they are sent by a publisher or delivered to a subscriber. Since this impacts the performance of the persistence service, message tracing is not generally recommended for production environments.

To enable message tracing, set the log level of all persistence services in the cluster to “msg:debug”. Then, for each client application that needs to trace messages, set the client’s loglevel to “msg:debug”. Both the persistence service leader and the client trace the messages.

Note: The persistence service can only trace messages for clients whose log level is “msg:debug”.

The persistence service log level is usually set in the FTL server yaml configuration file. For details, see Persistence Service Configuration Parameters”. The persistence service log level may also be set through the REST API while the persistence service is running.

For details, seePOST persistence/clusters/<clus_name>

The client log level is usually set through the client API call, tib_SetLogLevel (or language equivalent). The client’s log level may also be set via the REST API while the client is running. For details, see POST clients/<ID> and POST clients