Search queue waiting metric shows zero under normal load due to fast processing

SearchQueue waiting metric remains at 0 under normal and heavy load because Meilisearch processes searches faster than Prometheus polling intervals can capture. Queue prioritizes dequeuing, making non-zero values difficult to observe even under stress testing. Requires extreme concurrent load (10+ parallel loops with 1s artificial delays) to observe non-zero values.

When monitoring search queue health: (1) understand that 0 doesn't indicate absence of queue activity, (2) consider implementing rolling windows or max value tracking to capture peak states between polling intervals, (3) for load testing queue metrics, use 10+ concurrent request loops with 1s sleep delays to generate observable queue pressure, (4) if debugging search delays with consistently-zero waiting metrics, investigate other bottlenecks beyond queue pressure.