Multi-Machine Workers

Use this scenario when more than one machine participates in the same operational run.

First decision

Ask one question:

If any worker checks in, is the run still considered healthy, or does each worker need to prove its own progress?

If any worker is enough

Use Standard mode.

This works well when the overall system is what matters and individual worker silence is not a support issue on its own.

If each worker matters

Use Condition By Machine.

This works well when:

• each worker should keep processing independently
• you want per-machine errors and alerts
• one silent machine should not be hidden by activity from another machine

Add Expected Machine Count when needed

If the run should involve a minimum number of workers, configure Expected Machine Count so the watch does not fully clear until enough machines have reported.

Common example

A process is expected to fan out to five workers. Four workers check in, one never starts.

• Standard mode may still look healthy if the overall shared condition keeps receiving check-ins
• Condition By Machine with Expected Machine Count makes the missing worker visible