Tomasz Maruszak

@gnios that helps a lot. The headers in ASB would represent application properties of the message. If we need to get ahold of other properties of the message (content type...

Hi @gnios, I’ve opened a PR for this feature in #408 - feel free to take a look when you get a chance. The key change is in the [`IMessageSerializer`](https://github.com/zarusz/SlimMessageBus/pull/408/files#diff-b2122115f88429f445a25d037e82092eaa82b5e8d86e338fafe2a2287585a744)...

Please take a look at the linked PR. I'm happy to publish a pre-release so it can be tested and previewed early. I'd like to include this in the upcoming...

There is a [pre-release 3.3.0](https://www.nuget.org/packages/SlimMessageBus.Host.Serialization/3.3.0-rc202) version available if anyone wants to try this out. @gnios already tried and earlier pre-release, and it was meeting his expectations. Closing as done.

Newest API seems to be https://github.com/Azure/azure-sdk-for-net/blob/Azure.ResourceManager.EventHubs_1.1.0/sdk/eventhub/Azure.ResourceManager.EventHubs/README.md

hey @jaap-van-yperen please describe your use case, ideal API experience (propose one), and transport you want that in.

Thanks, @jaap-van-yperen. I’ll look into this further - I’ll do some research on SQS to understand what’s possible, then compare it with the other transports to see if we can...

Yes, I agree. The cluster should go into some error/undefined state. That state should then inform the user code to either stop serving requests or continue - ideally this could...

Hey @tjpeel-ee, A few thoughts and ideas: 1. Regarding the standard interceptor approach — since SMB uses `Microsoft.Extensions.Logging`, you might consider using `logger.BeginScope()` within the interceptor (wrapping `await next()`). It...

Hi @EtherZa, Thanks for the input and for sharing your examples! Regarding your OTEL interceptor setup — I’ve actually been considering building an OTEL plugin that would do exactly what...