Jeremy D. Miller

Might decide not to do this at all, but it was handy once upon a time.

See JasperRuntime.Logging.

See SagaFramePolicy. Use a custom exception with more context. Similar validation to what we did for projections in Marten

You need to use the Destination on the URI to immediately locate the right sending agent, and send it out that way. No routing, no lookup the message type, just...

Open Telemetry Support

1

See [messaging conventions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/messaging.md). * Span name for destination -> "[endpoint name] [message type]" * Span name for receiving? -> "[service name] [message type]" * Propagate correlation id & id *...

Really just making sure that `ConsumerOptions` and `ProducerOptions` are both exposed and usable from `PulsarEndpoint`. Might try to make the subscription name be configurable too, but use the service name...

Using either Rabbit MQ or Azure Service Bus, you should be able to interchange messages with an app using NServiceBus

Using either Azure Service Bus or Rabbit MQ, you should be able to exchange messages seamlessly between a Jasper app and a MassTransit app

And update the durable messaging docs with it too.