pliner / easygelf

GELF for log4net and NLog

easygelf's Issues

Change facility name via variable

Hi,

I wanna change the facility name via variable.

For example;

<target name="GelfUdp" xsi:type="GelfUdp" facility="${var:facilityName}" remoteAddress="127.0.0.1" remotePort="12103" layout="${message}"> <parameter name="_errorId" layout="${var:errorid}" /> <parameter name="thread" layout="${threadid}" /> </target>

I saw graylog in facility = ${var:facilityName} :)

Is there any way to do this?

Thanks.

Multiple hosts in appender

Null ref. exc.

plz fix property.Value != null
https://github.com/Pliner/EasyGelf/blob/master/Source/EasyGelf.NLog/GelfTargetBase.cs#L100

UDP Ephemeral Port Over Allocation

The current implementation creates a new ephemeral port for each chunked GELF message that is sent. This can cause issues with enterprise firewalls, as it leads to synthetic connections being left open for each IP, Local, Remote port combination. Its also orders of magnitude slower than reusing the same local port for each send.

Remove mandatory dependency on RabbitMQ

I've used your library to log to my GrayLog server and it works well, so thanks for that.

I'm only using the UDP target though, and I'm annoyed by the unneeded RabbitMQ dependency. It would be nice if everything RabbitMQ-related was split off into its own Nuget package.

GELF via HTTP Support?

Hi,

Quick question: does your library support GELF via HTTP? As described here:

http://docs.graylog.org/en/latest/pages/sending_data.html#what-are-graylog-message-inputs

thanks!

receiving data but no registering any message

I was using this plugin to send log to localhost in both tcp anda udp protocols and was working perfectly.I redirect to server but even the fact that both inputs are registering increasing the amout of data, not a single message was registered in neither inputs. I have no idea why this is happening

HTTP implementation incomplete

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

Amqp Appender: connect and publish in background thread

Configure GelfUpdAppender remote address/port at runtime

I am trying to keep most of log4net configuration externalized in xml for our apps, but with something like the UDP appender, I would need to route the log messages to a different address and/or port depending on what region (dev, test, or prod) the app is running in. I was thinking I could add the GelfUdpAppender in the xml configuration with a bogus address (or localhost), and then run-time re-configure the address. I tried this, and I got no errors, but the messages aren't delivered to the graylog listener, so I'm guessing that at this point, the appender has already created it's socket connection using the address from the xml configuration, and won't do so again. Do you have a recommendation on how such a thing could be accomplished? I could maintain region-specific log4net configurations, and bootstrap log4net with the right one, but I don't like the duplication (maintenance) that comes with this option. I think I could also just do all instantiation of the gelf appender in code - this is workable, I just prefered having MOST of the configuration of all appenders in the xml (for example, keeping all conversion patterns for all appenders in one place).

Thanks in advance for any suggestions you might have!

TCP Broken

Affects version 0.5.1.90 in Nuget

<target name="GelfTcp" type="GelfTcp" facility="TestApp" remoteAddress="graylog" remotePort="12201" layout="${message}" verbose="true" />

UDP works, but not TCP.

Use more lightweigh json library

Done

Add Amqp Transport to NLog

Done

Memory Leak

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 way to catch these exceptions?

Thank you!

Closed

Tcp Appender

Done

Add README

Add options descriptions for udp and amqp appenders(targets)

Nuget

Done

Amqp Appender: publishConfirms, persistent vs transient

Amqp Appender

Done

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...

Merge all external dependencies except log4net

Done

Amqp Appender: retries

Done

Simplify debuging

Add AdditionalFields to Log4Net appenders

Is there some specific reason why #16 wasn't merged?
It would be nice to be able to add additional fields using Log4Net as well. I'm happy to work on that PR or to create a new implementation which is closer to the Nlog one which already exists, but it would be good to understand why PR #16 wasn't merged.

Make EasyGelf compatible with .NET Standard 2.0

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