What would you monitor for Streams and Backpressure on-call?

Answers use simple, clear English.

Quick interview answer

On-call for Streams and Backpressure: alert on lag/latency, error spikes, and saturation — with runbooks. Baseline: Readable pushes data; Writable signals backpressure when internal buffer exceeds highWaterMark. Respect drain event before resuming writes to avoid memory blowup.

Detailed answer

On-call monitoring for Streams and Backpressure: • Golden signals: latency, traffic, errors, saturation • Streams and Backpressure-specific gauges (queue delay, pool wait, cache miss, etc.) • Alerting: burn-rate / multi-window so pages are actionable • Runbook: mitigate → diagnose → escalate Parent context: Baseline: Readable pushes data; Writable signals backpressure when internal buffer exceeds highWaterMark. Respect drain event before resuming writes to avoid memory blowup.

Full explanation

Tie each alert to a user-visible or SLO impact for Streams and Backpressure. Baseline: Readable pushes data; Writable signals backpressure when internal buffer exceeds highWaterMark. Respect drain event before resuming writes to avoid memory blowup.

Follow-up questions

Only answered follow-ups are shown — click to open with full answers

Parent context — Streams and Backpressure

Baseline: Readable pushes data; Writable signals backpressure when internal buffer exceeds highWaterMark. Respect drain event before resuming writes to avoid memory blowup.

View full parent question →

#node-streams-backpressure#architect