You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
yeah, I have a version for nlog that was cleaned up to do async and improved error handling. I've been meaning to get around to migrating the code over to this log4net version. I'll try to prioritize it for the next release.
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
The text was updated successfully, but these errors were encountered: