mantasaudickas / nlog.gelf Goto Github PK

hey guys, how to use to udp protocol?

udp://ip:12201

Hello,

Looking into this project I see it does not handle including any properties from the multiple NLog Diagnostic Contexts. Is this something that is being worked on or is something anyone has looked into?

I've done a very quick investigation and I found a way this could be implemented but wanted to check first if anyone has worked on this before.

If this is something that is still pending, I will be working in an implementation of this, I'll post updates here with the proposed API and configuration parameters so I can get feedback and to see if it's something that could be included in this library.

Regards.

Reduce allocations by having this check:

if (logEventInfo.Properties != null && logEventInfo.Properties.Count > 0)

When sending logs to server, wrong log level code is sent. It send log level code from NLog but GrayLog uses syslog's codes. Basically those are reverse.

If you look at http://docs.graylog.org/en/2.2/pages/gelf.html for field level it says "the level equal to the standard syslog levels;"

NLog levels can be viewed here: https://github.com/NLog/NLog/blob/master/src/NLog/LogLevel.cs
Syslog levels: https://en.wikipedia.org/wiki/Syslog#Severity_level

As you can see on this image, levelName and severity doesn't match.

Custom fields specified as LogEventInfo.Properties are not sent to server. They are not mapped to GelfMessage.Fields.

I've fixed it and created pull request.

@mantasaudickas Can you publish new nuget?

Is it possible to make NuGet package for .NET Framework 4.5.1?

Great package that does exactly what I'm after, so thank you!.

It does seem though that the connections to GrayLog aren't being closed? Im running a test console project and GrayLog is showing 101 connections and climbing. Should the Write method be creating a new GelfSender every time?