Short answer: preserve evidence before you optimize alert volume
For an e-commerce backend, use health endpoints for fast availability decisions and queue-aware task monitoring for customer-incident reconstruction. Choose the second as the source of truth when an order, payment, or fulfillment task can be delayed without making the process unavailable; choose the first when a dependency must fail closed within seconds. The boundary is evidence quality, not the number of checks.
A green /healthz response can coexist with a worker that has stopped acknowledging jobs. The inverse is also possible: a queue may contain old work while the HTTP process still answers every probe. Treating either signal as a complete health model creates noise for on-call engineers and a blank space in the incident record.
That gap is the signal.
What evidence does a customer incident actually need?
The useful unit is not a ping.…