Updated 8 days ago - 2 minutes to read

Logging with the WCF Diagnostics tracing feature

In your environment you may have multiple WCF Applications running on different servers. This means you may end up having tons of files to search. You may have different developers having enabled or tuned logging differently due to lack of governance. With Nodinite you get total control and a foundation for governance and an active documentation using our Repository Model. With Nodinite you can centralize logging and manage/share insights from logged events.

Nodinite Server
WCF Enabled Application
SMB
Pickup Service
WCF Diagnostic Tracing
Configuration file
Nodinite DLL files
WCF Application
Folder

Scenario: Basic Request/Response

In this scenario we have one or more Consumers of the WCF Application.

WCF ApplicationConsumerWCF ApplicationConsumerRequestResponse

WCF Tracing enabled

With the built-in WCF Tracing enabled the Request and the Response is caught by the framework and copied to the trace engine.

WCF Diagnostics TracingWCF ApplicationConsumerWCF Diagnostics TracingWCF ApplicationConsumerRequestLog RequestResponseLog Response

Nodinite Trace listener

When the Nodinite WCF Diagnostics tracing feature is enabled our component (DLL) will create a Json formatted Log Event and write it to the configured output folder. Eventually the Nodinite Pickup Service will consume these Log Events. This means that Nodinite will NOT waste your disk space and you do not have to setup any cleaning maintenance jobs.

Nodinite Trace ListenerWCF Diagnostics TracingWCF ApplicationConsumerNodinite Trace ListenerWCF Diagnostics TracingWCF ApplicationConsumerRequestLog RequestNodinite Log Event (Json)ResponseLog ResponseNodinite Log Event (Json)

Next Step

Now Add or manage Log Views and use the Log Views to view the WCF Diagnostic output.