Hardening FailureAck over long messages, more info about outgoing mes…

…sages

src/Transports/Azure/Wolverine.AzureServiceBus/Internal/AzureServiceBusSenderProtocol.cs

@@ -57,4 +57,4 @@ public async Task SendBatchAsync(ISenderCallback callback, OutgoingMessageBatch
             await callback.MarkProcessingFailureAsync(batch, e);
         }
     }
-}
+}

src/Wolverine/Runtime/MessageContext.cs

@@ -203,7 +203,7 @@ public async ValueTask SendFailureAcknowledgementAsync(string failureDescription
         var acknowledgement = new FailureAcknowledgement
         {
             RequestId = Envelope.Id,
-            Message = failureDescription
+            Message = failureDescription.Elid(200)
         };
 
         var envelope = Runtime.RoutingFor(typeof(FailureAcknowledgement))

src/Wolverine/Transports/Sending/SendingAgent.cs

@@ -83,8 +83,10 @@ Task ISenderCallback.MarkProcessingFailureAsync(OutgoingMessageBatch outgoing)
 
     public Task MarkProcessingFailureAsync(OutgoingMessageBatch outgoing, Exception? exception)
     {
+        var messageCounts = outgoing.Messages.GroupBy(x => x.MessageType).Select(x => $"{x.Key}:{x.Count()}").Join(", ");
+
         _logger.LogError(exception,
-            "Failure trying to send a message batch to {Destination}", outgoing.Destination);
+            "Failure trying to send a message batch to {Destination} with messages {Counts}", outgoing.Destination, messageCounts);
         _logger.OutgoingBatchFailed(outgoing, exception);
         return markFailedAsync(outgoing);
     }