Improve documentation in code and outside code

[Brunni]

Hi,

I'm very happy about this GELF Logging Extension, as I don't need to use serilog or NLog to get my logs into GrayLog interface.

But I would prefer some more documentation, e.g.

• Is this extension using async or sync logging? Is there a caching?
• What happens, if there are connection errors? Is there a retry or is the extension disabled for some time? Where are the logs?
• Is every message via HTTPS sent as a single request?

Also inside the code:

• Why is this method necessary? Why not use totalseconds?

  gelf-extensions-logging/src/Gelf.Extensions.Logging/GelfLogger.cs

  Line 69 in 22ee531

  private static double GetTimestamp()

I don't want to loose log messages, when using this extension and make sure, that everything is configured correctly.

[mattwcole]

This library is one of many 3rd party providers for Microsoft.Extensions.Logging that all work in a similar way. To answer your questions:

• Logging is of course async and there is no no caching (what would be cached?)
• Connection errors are swallowed silently, there are no retries and no internal logs
• Messages are sent according to the GELF specification 1 message at a time
• The GetTimestamp() method is used to populate the timestamp property in the GELF spec