docs: Introduce troubleshooting guide for Azure Service Bus

[tomkerkhove]

Based on kedacore/keda#5227, I had a quick idea to start introducing troubleshooting guides to reduce the load on maintainers/community and document recurring issues.

Currently this is added to the same page as the scaler, but we should integrate scalers in to our existing "troubleshooting" section over time.

Checklist

• Commits are signed with Developer Certificate of Origin (DCO)

Relates to kedacore/keda#5227

[netlify]

✅ Deploy Preview for keda ready!

Name	Link
🔨 Latest commit	e7c37f4
🔍 Latest deploy log	https://app.netlify.com/sites/keda/deploys/65a654d17bac460008e187ce
😎 Deploy Preview	https://deploy-preview-1269--keda.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Thank you for your contribution! 🙏 We will review your PR as soon as possible.

While you are waiting, make sure to:

• Add your contribution to all applicable KEDA versions
• GitHub checks are passing
• Is the DCO check failing? Here is how you can fix DCO issues

Learn more about:

• How to become a listed end-user or a listed commerical offering
• Our contribution guide

[tomkerkhove]

What do you think about this idea @zroubalik / @JorTurFer

[JorTurFer]

Maybe we can create a new secction for these stuff, and include FAQ and troubleshooting pages. Troubleshooting info looks quite fragmentated between FAQ, troubleshooring, and now in page

[JorTurFer]

Just to clarify, I'd move to a versioned section, because fixes related with v2.X can apply to v2.Y or not

[tomkerkhove]

I agree and that is also why I added this:

Currently this is added to the same page as the scaler, but we should integrate scalers in to our existing "troubleshooting" section over time.

However, I am not sure if we should do it now already or in the future. Currently I think we should just add this to scalers for now and once we have more scenarios we can look at how we can support it and what the needs are (instead of assuming)

[JorTurFer]

yeah, definitivelly!
Let's add close to the scalers for the moment, but let's start to think about how we can improve the troubleshooting sections for the future. Let me open an issue to track it

[JorTurFer]

#1270

[zroubalik]

Is this relevant only to 2.12?

[JorTurFer]

Is this relevant only to 2.12?

I think that it's interesting in general

[tomkerkhove]

@zroubalik @JorTurFer as mentioned above, wanted to know if you think it's the right place to start before applying it everywhere.

I think that is not fully answered yet, once it is I will expand it to all versions

[tomkerkhove]

Shall we merge this or do we look for alternative ways @zroubalik @JorTurFer ?

[JorTurFer]

We can merge it IMO (but add it to v2.13 too)

[tomkerkhove]

Ugh I love GitHub codespaces messing up DCO