Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Introduce troubleshooting guide for Azure Service Bus #1269

Merged
merged 3 commits into from
Jan 16, 2024
Merged

docs: Introduce troubleshooting guide for Azure Service Bus #1269

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8b7ad4c
docs: Introduce troubleshooting guide for Azure Service Bus
tomkerkhove Jan 16, 2024
93d34f6
Update content/docs/2.13/scalers/azure-service-bus.md
tomkerkhove Jan 16, 2024
e7c37f4
Merge branch 'main' into tomkerkhove-patch-1
tomkerkhove Jan 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions content/docs/2.12/scalers/azure-service-bus.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
11 changes: 11 additions & 0 deletions content/docs/2.13/scalers/azure-service-bus.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)