Scheduling Dispatcher
Multi-instance operations · Azure Monitor telemetry
Loading Azure Monitor telemetry…
Avg cycle
—
milliseconds
Avg dispatch
—
milliseconds
Devices processed
—
completed events
Devices dequeued
—
accepted for processing
Exceptions
—
recorded exceptions
Queue added
—
devices
Queue removed
—
devices
Immediate intercepts
—
received/promoted
Avg device processing
—
milliseconds
Avg queue age
—
milliseconds enqueue → dequeue
Avg due lateness
—
milliseconds past due
Avg queue depth
—
after dequeue
Controls succeeded
—
actual commands
Controls failed
—
failed or unsupported
Cycle and dispatch duration
CycleDispatch
Observed instances
Device lifecycle · all devices
Queue and processing insights · by group and control intent
NoControl means processing completed with a DoNotControl directive. Dequeued; no completion in range means queue telemetry exists but no matching processor completion was observed in the selected window. Legacy telemetry means completion telemetry predates the ControlIntent field.
| Group | Intent | Samples | Queue age | Due lateness | Processing | Queue depth |
|---|
CPU utilization · 0–100%
Memory usage · working set / available
Queue depth over time
Actual control commands
| Group | Command | Action | Outcome | Count | Avg duration |
|---|
Exceptions by type over time
Top 10 exception signatures
| Exception type / problem | Count | Last seen | Investigation |
|---|
Telemetry coverage: manufacturer/category dequeue grouping starts when the enhanced telemetry version is deployed; older data contains processed manufacturer only. Control-command-issued counts are not emitted yet and are intentionally not inferred. Data can trail live activity due to Azure Monitor ingestion latency. Restrict this operational endpoint with App Service access restrictions until application authentication is added.