From 8b7ad4c203e195e6745285a75f5a38c4272e46d2 Mon Sep 17 00:00:00 2001 From: Tom Kerkhove Date: Tue, 16 Jan 2024 10:04:10 +0000 Subject: [PATCH 1/2] docs: Introduce troubleshooting guide for Azure Service Bus Signed-off-by: Tom Kerkhove --- content/docs/2.12/scalers/azure-service-bus.md | 11 +++++++++++ content/docs/2.13/scalers/azure-service-bus.md | 12 ++++++++++++ 2 files changed, 23 insertions(+) diff --git a/content/docs/2.12/scalers/azure-service-bus.md b/content/docs/2.12/scalers/azure-service-bus.md index ae14d0791..5668b83d7 100644 --- 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 index ae14d0791..ce4eddbb1 100644 --- a/content/docs/2.13/scalers/azure-service-bus.md +++ b/content/docs/2.13/scalers/azure-service-bus.md @@ -107,3 +107,15 @@ 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) + From 93d34f662976adea1d2edbba2d0ab1b3a64e9891 Mon Sep 17 00:00:00 2001 From: Tom Kerkhove Date: Tue, 16 Jan 2024 11:04:48 +0100 Subject: [PATCH 2/2] Update content/docs/2.13/scalers/azure-service-bus.md Signed-off-by: Tom Kerkhove --- content/docs/2.13/scalers/azure-service-bus.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/docs/2.13/scalers/azure-service-bus.md b/content/docs/2.13/scalers/azure-service-bus.md index ce4eddbb1..5668b83d7 100644 --- a/content/docs/2.13/scalers/azure-service-bus.md +++ b/content/docs/2.13/scalers/azure-service-bus.md @@ -118,4 +118,3 @@ 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) -