Follow-up · depth 7
What would you monitor for L4 vs L7 Load Balancing on-call?
What would you monitor for L4 vs L7 Load Balancing on-call?
Answers use simple, clear English.
Quick interview answer
On-call for L4 vs L7 Load Balancing: alert on lag/latency, error spikes, and saturation — with runbooks. Use L4 vs L7 Load Balancing as the core idea. Example shape: ALB routes /api → API target group, /static → S3; NLB for gRPC TCP passthrough..
Detailed answer
On-call monitoring for L4 vs L7 Load Balancing: • Golden signals: latency, traffic, errors, saturation • L4 vs L7 Load Balancing-specific gauges (queue delay, pool wait, cache miss, etc.) • Alerting: burn-rate / multi-window so pages are actionable • Runbook: mitigate → diagnose → escalate Parent context: Use L4 vs L7 Load Balancing as the core idea. Example shape: ALB routes /api → API target group, /static → S3; NLB for gRPC TCP passthrough..
Full explanation
Tie each alert to a user-visible or SLO impact for L4 vs L7 Load Balancing. Use L4 vs L7 Load Balancing as the core idea. Example shape: ALB routes /api → API target group, /static → S3; NLB for gRPC TCP passthrough..
Follow-up questions
Only answered follow-ups are shown — click to open with full answers
Parent context — L4 vs L7 Load Balancing
Use L4 vs L7 Load Balancing as the core idea. Example shape: ALB routes /api → API target group, /static → S3; NLB for gRPC TCP passthrough..
View full parent question →