Messaging Bridge "bridge.error" queue - how to handle it?

1

I’m trying to set up a service using the Messaging Bridge to forward messages from an SQL transport to an Azure Service Bus transport. As I understand it, each transport must have a “bridge.error” queue. However, I’m unsure how I should handle messages ending up in this queue?

Ideally, I want to be able to monitor it with ServicePulse/ServiceControl, which we use for all other NServiceBus monitoring. But the documentation for “bridge.error” seems a bit vague to me. I get the impression that I’m kind of left hanging, having to build my own tool for monitoring the queue and handle retries. Is there any way to handle “bridge.error” using ServicePulse/ServiceControl?

2

According to the docs “The bridge can be configured to allow a single ServiceControl installation to manage and monitor endpoints on all bridged transports.” The problem is when the bridge fails to send to messages to side or another it won’t be able to put it’s errors into a queue that service control reads from. There is an open issue that you may follow and add a comment of interest if this is important for your scenario.