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
{{ message }}
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
When calling Trace.Flush(), some of the last messages may be lost. Per this, TelemetryClient.Flush needs to be called to make sure the last batch is sent.
The text was updated successfully, but these errors were encountered:
A similar issue exists in ApplicationInsightsAppender (Log4NetAppender). ApplicationInsightsAppender doesn't override AppenderSkeleton.Flush(), so calling Flush just hits AppenderSkeleton.Flush().
I haven't experimented with ApplicationInsightsTarget (NLogTarget), but I'd expect the same issue to exist there, since there doesn't appear to be anything calling TelemetryClient.Flush()
I am not familiar with NLog, but I looked for AppenderSkeleton.Flush() before I put in my PR and was unable to find it. The version that is referenced doesn't implement the IFlushable interface in the latest code. To my eye, this seems to be the issue with #68.
When calling Trace.Flush(), some of the last messages may be lost. Per this, TelemetryClient.Flush needs to be called to make sure the last batch is sent.
The text was updated successfully, but these errors were encountered: