EventHub 发送消息，但 Application Insights 上的 System.Net.Sockets.SocketException

Question

I have this code below that sends message to azure EventHub, at first it works fine

public async Task SendMessage(string message) {
            
    var producer = new EventHubProducerClient(this.connectionString, this.eventHubName);
   
    using (EventDataBatch eventBatch = await producer.CreateBatchAsync()) {
        if (!eventBatch.TryAdd(new EventData(message))) {
            throw new Exception($"Event is too large for the batch and cannot be sent.");
        }

        try {
            await producer.SendAsync(eventBatch);
        }
        catch(Exception ex) {
            saveLog(message, ex);
        }
        finally {
            await producer.DisposeAsync();
        }
    }
}

but in Application Insights I'm facing this message exception:

A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

Exception type:

System.Net.Sockets.SocketException

I've tried to add a ContinueWith (OnlyOnFaulted or OnlyOnCanceled), as below, to log it, but now I get in the catch Exception (not in ExceptionHandle ) as "A task was canceled"

try {    
  await producer.SendAsync(eventBatch)
   .ContinueWith(t => ExceptionHandle(t, message), TaskContinuationOptions.OnlyOnFaulted);
                }

How can I handle these exceptions that App Insights display?

Answer 1

If you need to handle the task exception by using a ContinueWith ( OnlyOnFaulted or OnlyOnCanceled ) we can get this exception in catch block only. By default, if the task runs successfully, it throws Exception if the Task IsFaulted we can get the exception from Catch Block .

To fix this issue:

Use UnobservedTaskException event which observe the Task Exceptions and it doesn't terminate by default. The exception can be handled by the runtime .