EasyGelf issues

Make serializer a little more forgiving when keys collide.

Thanks for sharing this project. This PR addresses something we saw in a production environment where pushed an nlog config change that referenced MDC items in the GelfTcp target that...

jeffgoo

Fix headers and syntax highlighting in README

Gosha

TCP target exceptions

Hello, we want to use EasyGelf via TcpTarget, but right now we cannot catch any exceptions while opening a connection or sending a message to GrayLog server. Is there any...

Martynas91

Make EasyGelf compatible with .NET Standard 2.0

1

Well, .NET Core is slowly becoming mainstream and we need a possibility to use this package in portable applications.

MrDaedra

Change facility name via variable

Hi, I wanna change the facility name via variable. For example; ` ` I saw graylog in facility = ${var:facilityName} :) Is there any way to do this? Thanks.

mehmetcakmaz

Not work with NLog 4.4.12

I create empty console c# project. Add EasyGelf from Nuget packet manager. It view on NLog 3.2.0. I update NLog to latest version 4.4.12 and easygelf doesn't work. I'm cry...

coolfrik

HTTP implementation incomplete

I've tried to use HTTP POST input through current version but the implementation is incomplete.

staticdev

It is possible to notice if Graylog connection is lost.

Originally EasyGelf swallows all exceptions. I want to use EasyGelf with TCP-protocol to get connection lost -errors. I have NLOG fallbackgroup that should notice if Graylog connection is lost. In...

akselila