| all
|
Tune logging for all elements, embracing all the categories in this table.
|
| application
|
Tune logging related to the application program, such as the program’s use of API calls, message formats, and content matchers.
|
| IO
|
Tune logging related to data I/O, such as message data entering or leaving the program, and message packetization.
|
| RS
|
Tune logging related to the realm server.
- In FTL server client processes, this category includes client communication with the FTL server.
- In FTL server processes, this category includes operations within the FTL server, such as communication with clients, with affiliated FTL servers, and with services.
|
| transports
|
Tune logging related to transports, including peer connections, subscriber interest, message send operations, protocols.
|
| store
|
Tune logging related to persistence stores and durables, such as store and durable operations, quorum formation, and leader election.
|
| msg
|
Tune logging related to messages. The debug level logs each outbound message send and each inbound message callback by printing a representation of the message.
|
| broker
|
Tune logging related to clients of the eFTL service. (This element is available
only in the eFTL service.)
|
| route
|
Tune logging related to wide-area durables.
|
| mux
|
Tune logging related to the FTL server as it redirects HTTP requests to the services it provides.
|
