Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COYes, we would like to correlate the logging between the client and the server. Let's assume that the client is actually a .NET 4.0 client (not Silverlight because Silverlight does not support Trace.CorrelationManager.*). The client can set Trace.Correlationmanager.ActivityId = <new guid>. If logging captures that value then every logging statement can be tagged with the ActivityId. Now, if we can get that ActivityId to the Server, then logging statements from the server can also tag each logging statement with the ActivityId. If all logging for all clients and servers ...
      singulars
    2. CO... is directed to the same place, let's say a database, then we could query for all logging messages with the same ActivityId, order them by time, and we would be able to see the logging from the server(s) that corresponds to calls from the client. This is available "free" to some extent through WCF ActivityId propogation (as linked in my original question) if you using System.Diagnostics logging/tracing. I am interested in finding out how/if ActivityId propogation integrates with non-System.Diagnostics logging/tracing such as log4net and NLog.
      singulars
    3. COThere are issues using WCF ActivityId propogation with Silverlight clients because Silverlight does not support Trace.CorrelationManager.*, so there is already some work to do to even be able to "start" the Activity in Silverlight.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload