Report
From Azure Storage Queue document, queue messages should be set to invisible state when pulled from queue for processing, deleted when processing completes and be visible again when processing fails. So when computing queue length for scaling, it's better to consider both visible and invisible messages like in the get-queue-length documentation instead of counting those visible only.
Expected Behavior
Use correct queue length to count both visible and invisible messages.
Actual Behavior
Count only visible messages.
Steps to Reproduce the Problem
None
Logs from KEDA operator
KEDA Version
None
Kubernetes Version
None
Platform
None
Scaler Details
Azure Storage Queue
Anything else?
No response
Report
From Azure Storage Queue document, queue messages should be set to invisible state when pulled from queue for processing, deleted when processing completes and be visible again when processing fails. So when computing queue length for scaling, it's better to consider both visible and invisible messages like in the get-queue-length documentation instead of counting those visible only.
Expected Behavior
Use correct queue length to count both visible and invisible messages.
Actual Behavior
Count only visible messages.
Steps to Reproduce the Problem
None
Logs from KEDA operator
KEDA Version
None
Kubernetes Version
None
Platform
None
Scaler Details
Azure Storage Queue
Anything else?
No response