docs: Introduce troubleshooting guide for Azure Service Bus (kedacore…

…#1269)
sbarnesthornton · Jan 16, 2024 · fb21829 · fb21829
1 parent 48abceb
commit fb21829
Show file tree

Hide file tree

Showing 2 changed files with 22 additions and 0 deletions.
diff --git a/content/docs/2.12/scalers/azure-service-bus.md b/content/docs/2.12/scalers/azure-service-bus.md
@@ -107,3 +107,14 @@ spec:
     authenticationRef:
         name: azure-servicebus-auth # authenticationRef would need either podIdentity or define a connection parameter
 ```
+
+### Troubleshooting
+
+#### KEDA is unable to get queue information due to "invalid queue runtime properties: no CountDetails element"
+
+When KEDA logs show errors similar to `invalid queue runtime properties: no CountDetails element` it usually is caused because of throttling by Azure Service Bus.
+
+Consider applying one of the following mitigations:
+- Scaling the Azure Service Bus namespace to a higher SKU, or use premium
+- Increase the polling interval of the ScaledObject/ScaledJob
+- Use [caching of metrics](./../concepts/scaling-deployments/#caching-metrics)
diff --git a/content/docs/2.13/scalers/azure-service-bus.md b/content/docs/2.13/scalers/azure-service-bus.md
@@ -107,3 +107,14 @@ spec:
     authenticationRef:
         name: azure-servicebus-auth # authenticationRef would need either podIdentity or define a connection parameter
 ```
+
+### Troubleshooting
+
+#### KEDA is unable to get queue information due to "invalid queue runtime properties: no CountDetails element"
+
+When KEDA logs show errors similar to `invalid queue runtime properties: no CountDetails element` it usually is caused because of throttling by Azure Service Bus.
+
+Consider applying one of the following mitigations:
+- Scaling the Azure Service Bus namespace to a higher SKU, or use premium
+- Increase the polling interval of the ScaledObject/ScaledJob
+- Use [caching of metrics](./../concepts/scaling-deployments/#caching-metrics)