# Use a per-queue observation for responsive Queue workload decisions

> DSE recommends documenting the decision’s required freshness and the specific queue before selecting a metric.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-154-use-a-per-queue-observation-for-responsive-queue-workload-decisions/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:32:26+00:00
- Modified: 2026-09-17T16:46:28+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: IT
- Reading time: 1 minutes

## What you need to know

DSE recommends documenting the decision’s required freshness and the specific queue before selecting a metric.

## Potentially affected

This applies when an operations team is choosing a backlog observation for Azure Queue Storage and needs to decide whether a worker workload should be adjusted.

## DSE recommendation

DSE recommends documenting the decision’s required freshness and the specific queue before selecting a metric.

## Article

## Source facts

Microsoft describes QueueMessageCount as a storage-account-wide queue message metric refreshed daily. For dynamic workload adjustments, the guide recommends querying each queue’s approximate message count. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/queues/queues-storage-monitoring-scenarios)

## Applicability

This applies when an operations team is choosing a backlog observation for Azure Queue Storage and needs to decide whether a worker workload should be adjusted.

## DSE recommendation

DSE recommends documenting the decision’s required freshness and the specific queue before selecting a metric. Keep account-level reporting distinct from the per-queue observations used for responsive action. Record that the direct count is approximate and choose an observation interval appropriate to the workload. Ask the application owner to define a bounded response and the conditions for stopping or reversing it, rather than making an unbounded change from a single count.

## Verification

Capture the observation time, queue identity, and approximate count alongside worker activity during a controlled test. Compare the proposed action with the workload’s agreed completion and stability criteria. Recheck after the action and retain the resulting evidence. Do not describe a daily aggregate as the instantaneous backlog of a particular queue or report improved processing without observing the workload result.

## Official references

- [Microsoft: Best practices for monitoring Azure Queue Storage | Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/queues/queues-storage-monitoring-scenarios)

## Primary reference

- Name: Best practices for monitoring Azure Queue Storage | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/storage/queues/queues-storage-monitoring-scenarios
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Use a per-queue observation for responsive Queue workload decisions,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-154-use-a-per-queue-observation-for-responsive-queue-workload-decisions/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.