When there are errors on the servicebus we don't log it. It would help if we logged errors for troubleshooting purposes.
When there are issues with the servicebus it is not possible to see what went wrong many times. You can go to the servicebus and look at the graph and see that there are "server errors" and "user errors" and "throttled messages"but there is no way to see the details of the server errors or the user errors.
Some times we can see a log entry in the CMS logs but not always and I guess it depends on the type of error.
If we had more information it would help when troubleshooting customers having problems with the servicebus.
Josef Kim
shared this idea
-
Jakob Hellsten
commented
To be able to trouble shoot we need to have insights in failed vs ok service bus messages.
As partners and end customers we also need to know how many messages that we use based upon the service bus tier we are using.
-
worked with some tickets that have no log from the service bus, so we have to handle it with our own tool and it really blocked us from investigating the issue.
I think this is really helpful to make the troubleshooting stage go faster with the best result.
