Queue-Based Monitoring

Use this pattern when one workflow can run against different queues and each queue should be monitored independently.

The problem

A single performer process may serve several customers, regions, or business streams. If you use one shared watch without queue awareness, a healthy queue can hide a stalled queue.

Recommended design

Use a missed-action watch with Condition By Queue so each queue keeps its own timing and error state.

Why it helps

• avoids creating a separate watch for every queue
• preserves independent health for each queue
• keeps alerts tied to the affected queue, not just the overall process

Check-in pattern

• include the queue identifier in the check-in
• activate and deactivate the queue-aware run using the same monitoring design
• optionally combine queue tracking with multi-machine processing inside that queue

Best fit

This pattern is especially useful when:

• the same codebase works several queues
• different queues start and finish at different times
• support teams need to know exactly which queue is at risk