Repro steps
Customers use the Service Bus extensions very frequently.
If these don't work then we need to ask the customer for the details of those Service Bus Namespaces to see if there is an issue on that side.
Adding this information when the Service Bus bindings starts would allow us to be able to
a) Build Detectors that access this information if the customer does raise a support request.
b) Look at automated solutions that will check connectivity to the Service Bus Namespace and allow the customer to resolve transient issues on their own.
Expected behavior
A log entry is written when we attach to the binding.
Actual behavior
We log information about the Service Bus Namespace but not the FQDN of the Service Bus namespace. It would also be great to document if this is a Queue or Topic listener.
Repro steps Customers use the Service Bus extensions very frequently. If these don't work then we need to ask the customer for the details of those Service Bus Namespaces to see if there is an issue on that side. Adding this information when the Service Bus bindings starts would allow us to be able to a) Build Detectors that access this information if the customer does raise a support request. b) Look at automated solutions that will check connectivity to the Service Bus Namespace and allow the customer to resolve transient issues on their own.
Expected behavior A log entry is written when we attach to the binding.
Actual behavior We log information about the Service Bus Namespace but not the FQDN of the Service Bus namespace. It would also be great to document if this is a Queue or Topic listener.
Known workarounds No workarounds exist.