-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log the payload the NLogViewer/network target to the InternalLogger #1708
Comments
It looks like this isn't logged to the InternalLogger. We could add it in the next version. The code should added to the |
Oh nice then :)
|
Do you mean, how to enable? That will be
Yes, also I think you will get a notification when the PR is linked to this issue :) |
I said
and you said
and I was actually really trying to say .. would an example be provided that uses this |
Sorry about the confusion. NLogViewer inherits from NetworkTarget, so if we log at NetworkTarget level, this is fixed for NLogViewer :) |
I have added some internal logs in NLog 4.3.11. https://www.nuget.org/packages/NLog/4.3.11 |
Thank you kindly! |
Type: Question
NLog version: 4.3.10
Platform: .Net 4.5
Current NLog config
Hi 👋
I'm trying to figure out a way to see the payload that is sent over the wire when using an
NLogViewer
target. My reasoning is that we use a viewer called Sentinal and I'm starting to use properties to attach more meta data, per log entry. (We use Serilog + Serilog.sinks.nlog right now).If i can see the exact payload that is sent over the wire to sentinal I can then determine if it's worth my time in trying to fix their application to handle dynamic columns (1 per property, for example) or maybe flatten the properties into the end of the rendered Message.
So - is there an easy way to see this data?
I'm used to using FIDDLER for snooping this type of info but this isn't HTTP traffic.
NOTE: If you noticed, i've added a
internalLogLevel="Trace"
attribute to see if the internal tracing might output/dump the payload context, but it doesn't. (I don't put that on any of my nlog files .. just this R&D).cheers!
The text was updated successfully, but these errors were encountered: