How it works

There is no magic here - WCF offers global hooks to reach into the message pipeline. Message inspectors (like the one used by Lumberjack) get their hands on WCF messages before they are routed to the service code and after the service has executed. Lumberjack's message inspector collects the data from the message request/response and submits the results to a TCP endpoint (port 8082).
The logging endpoint queues messages in an in-memory-queue and then writes the entries to a LiteDB database.