Currently, logs sent to HttpEventCollectorSender are flushed synchronously using FlushSync(). See
I can see this is advantageous over fire and forget in that exceptions are not lost. However, if the http requests to the Splunk system hang so does the application. Moreover, I use a mock api (WireMock) and delayed the response by a significant amount of time. The entire app hangs on any logging calls. My suggestion is to use FlushAsync().
I'd be more than happy to make a pull request for this, but I currently don't have permissions to make new branches.
Thanks!
Cory
Currently, logs sent to HttpEventCollectorSender are flushed synchronously using FlushSync(). See
log4net.Appender.Splunk/src/log4net.Appender.Splunk/SplunkHttpEventCollector.cs
Line 81 in c5b5b68
I can see this is advantageous over fire and forget in that exceptions are not lost. However, if the http requests to the Splunk system hang so does the application. Moreover, I use a mock api (WireMock) and delayed the response by a significant amount of time. The entire app hangs on any logging calls. My suggestion is to use FlushAsync().
I'd be more than happy to make a pull request for this, but I currently don't have permissions to make new branches.
Thanks!
Cory