Azure FAQ: Tips and tricks to diagnose issues in the about docs.particular.net

[dannycohen]

@yvesgoeleven - shall we rename the GH issue as "troubleshooting article on Azure hosting / transport" ?
I think we need one to catch all the misc. issues.

[yvesgoeleven]

Like a FAQ? My plan was to describe the techniques, not the concrete issues, would you like to do the latter?

[dannycohen]

FAQ would be just as good (as I see it, its a matter of phrasing the problem a differently)

[dannycohen]

Content proposal

See customer questions from https://nservicebus.desk.com/agent/case/4515

[yvesgoeleven]

Sounds like we're not on the same page here, or that we have multiple doco articles to write. I was more thinking in the lines of:

• My worker role is in an infinite reboot cycle since hosting my nservicebus endpoint: how do I diagnose what's going on?
• I'm getting connection refused exceptions when deploying to production: how do I diagnose what's going on.
• Etc....

[dannycohen]

@yvesgoeleven - that sounds like troubleshooting, and I totally agree we need those. But do you think there's value in adding Q&A's like the ones in https://nservicebus.desk.com/agent/case/4515 ?

[yvesgoeleven]

Yes, definitly

[dannycohen]

Sounds good. I suggest you consider how to organize the troubleshooting topics / Q&As and apply it as you see fit.

[dannycohen]

@yvesgoeleven - This also seems like a good topic:

known issue when enabling NServiceBus in a website that is host in the Microsoft Azure compute emulator

Particular/PlatformInstaller#106 (comment)

[yvesgoeleven]

Yes indeed, needs to be on the FAQ (at least until it's fixed)

[johnsimons]

Can we start publishing the list and keeping on adding extras as we go ?
@yvesgoeleven if you start dumping all the info this issue, I can to the editing and publishing it, thoughts ?

[SimonCropp]

seems this one is dead. closing