If I have async logging turned on in nlog.config, where is the ThreadID captured?
Context: I'm starting a greenfield project using .NET, Rx, and TPL Dataflow (a.k.a. TDP). It will make heavy use of async operations and background work queues.
Goal: In my logging I'd like to capture the ManagedThreadId where the work is being performed, and when work is being done in parallel (easy to get wrong in Rx, where default scheduler isn't ThreadPool). If I have async logging turned on in nlog.config, where is the ThreadID captured?
Concern: I don't see ThreadID in the core LogEntry class for NLog. For example it isn't sent to the browser in cbley/NLog.SignalR. If I have async logging turned on in nlog.config, where is the ThreadIDcaptured? If it isn't captured until the log entry is rendered (in an NLog background thread), then theThreadId is useless to me and I need to find a more appropriate logging library.
--
You received this message because you are subscribed to the Google Groups "NLog-Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nlog-users+...@googlegroups.com.
To post to this group, send email to nlog-...@googlegroups.com.
Visit this group at http://groups.google.com/group/nlog-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.