We are using the Messaging Bridge to bridge between our ASB and SQL transport endpoints. We have ServiceControl set up to use the SQL transport. In ServicePulse, we can see critical time and success and failure rates for endpoints on both the SQL and ASB transport. However, we do not get queue length information in ServicePulse for our ASB transport endpoints. Is there a way to do that?
Hey @stevebering
Edit: this is incorrect. See the next post for details.
The fact that you’re seeing some of the metric data appearing in ServicePulse means that the bridge is correctly forwarding the metric data.
Can you confirm that you have the NServiceBus.Metrics.ServiceControl package installed in your endpoint AS WELL AS the NServiceBus.Metrics.ServiceControl.MSMQ package installed? Both of them need to be added to the MSMQ endpoint in order for the queue length to be included in the metric data that is sent to ServiceControl.
Sorry @stevebering,
I noticed now that you’re using SQL and ASB and are trying to get the queue length from the ASB instance. MSMQ is not involved at all.
It is unfortunately not possible to get the queue length from ASB to show in your ServiceControl instance connected to SQL. The reason is:
The queue length is only sent as part of the metric messages for MSMQ, not any of the other transports. All other transports get their queue length provided directly by ServiceControl. So ServiceControl queries the underlying broker to get the queue length. This means that there is no way for the ASB queue length to show up in the metrics dashboard.
William,
That is disappointing, but I appreciate you getting back to me on this.
Thanks, Steve
Thanks for understanding Steve,
I’ve created a feature request on your behalf for this functionality. There’s no guarantee of when this will get picked up and implemented, but if I haven’t captured the need correctly I’d appreciate you commenting on the issue to provide more context.
1 Like