Dashboard/System design/15. Monitor Client-Side Errors

SYSTEM DESIGN · LESSON 15 OF 52 · 4 MIN VIDEO · 2 TOPICS

Monitor Client-Side Errors

Module Progress (0 / 2 Lessons Completed)0%
System design Track (0 / 52 Modules) · Overall 0/80 (0%)0%
⌁

Narrated HD Video Lesson (4 min) · Pro

Lesson Overview + Section #01 + RESHADED Checklist + Quiz #1 are unlocked free below (no login required). Unlock all 80 HD video lessons and deep-dive sections — or watch our two free sample video lessons first.

0% READSec 01/02 · Focus on Client-Side Errors in a Monitoring System
SYSTEM DESIGN VIDEO LESSON & GUIDE

Monitor Client-Side Errors

A service can be completely unreachable for millions of users while every internal server dashboard remains 100% green because DNS failures, ISP BGP blackholes, expired TLS certificates, and browser script crashes terminate requests before a single packet reaches backend load balancers. A Client-Side Monitoring system closes this observability blind spot by combining deterministic global Synthetic Probes with statistically sampled Real User Monitoring (RUM) and browser-native W3C Network Error Logging (NEL). In L4-L6 interviews, candidates are evaluated on enumerating pre-ingress failure modes, contrasting synthetic baselines against real-user ASN coverage, enforcing strict out-of-band collector isolation (separate domain, DNS, and ASN), and sizing privacy-safe session sampling.

WHAT YOU WILL MASTER IN THIS LESSON
  • Trace the pre-ingress client request path (Device -> DNS -> ISP/BGP -> CDN/TLS -> Load Balancer) to explain why upstream outages produce zero server-side errors.
  • Contrast active Synthetic Probes against passive Real User Monitoring (RUM + NEL) across nocturnal baseline stability and last-mile ISP coverage.
  • Architect an out-of-band telemetry ingestion pipeline with zero shared DNS, certificate, CDN, or ASN dependencies on the primary product.
  • Configure W3C NEL and Reporting-Endpoints headers alongside client-side local storage buffering to capture DNS/TCP/TLS failures even when app bundles fail to load.
  • Size session sampling (50M * 1% = 500,000 reports/day) and multi-dimensional stream aggregation by (region, ASN, error_type).
SYSTEMATIC BUILDING-BLOCK CHECKLIST (FROM MODULE 01)

4-Point Infrastructure Primitive Audit

Check off each dimension as you study this building block—interviewers test what it solves, how it works inside, what it costs, and how it fails.

0 / 4 Checked
INTERVIEWER SCORECARD · WHAT MAKES A STRONG HIRE?

5 Signals Bar Raisers Grade (L4 vs. L5 Senior vs. L6 Staff)

Senior (L5 / E5 / Senior SDE) Bar — Autonomous Pacing, Depth & Proactive Trade-Offs: Owns the 45-minute clock without prompting, derives every component quantitatively, surfaces failure modes (hot shards, stampedes, dual writes) BEFORE being asked, and defends consistency vs. latency trade-offs.
1. Scoping
✓ STRONG HIRE SIGNAL

Clarifies users, read/write skew, p99 latency, consistency bounds, and explicit non-goals in minutes 2–8.

✗ NO-HIRE RED FLAG

Jumps straight into drawing load balancers and microservices at minute 2 without asking a single question.

2. Right-Sized Design
✓ STRONG HIRE SIGNAL

Starts with the simplest working architecture justified by the math (e.g., 1 NVMe SQL primary + replicas + Redis for 40 writes/s & 3 TB).

✗ NO-HIRE RED FLAG

Recites a memorized Kafka + multi-DC Cassandra diagram that contradicts their own traffic calculations.

3. Technical Depth
✓ STRONG HIRE SIGNAL

Drives deep into 1–2 hard bottlenecks (partition keys, hot-key mitigation, transactional outbox, KV-cache batching) at minute 27.

✗ NO-HIRE RED FLAG

Skims across 12 boxes at identical buzzword depth and runs out of time before the deep dive.

4. Explicit Trade-Offs
✓ STRONG HIRE SIGNAL

Uses 3-part reasoning: 'A queue here because SMTP spikes to 3 s; checkout stays <60 ms, and we accept eventual email delay + retry dedup.'

✗ NO-HIRE RED FLAG

Name-drops tools ('We put Kafka and ZooKeeper here') without stating the alternative or operational cost.

5. Communication
✓ STRONG HIRE SIGNAL

Thinks aloud every 30–45s, checks alignment at phase transitions, and treats 'What if X fails?' as a cue for where points are awarded.

✗ NO-HIRE RED FLAG

Goes silent for 5 minutes while drawing or defends a flawed assumption defensively when nudged.

ARCHITECTURE & DATA-FLOW SLIDES · SLIDE 1 OF 1Section 01: Focus on Client-Side Errors in a Monitoring System
ARCHITECTURE / DATA FLOW DIAGRAM
your site is downUsersregion Aexpired record?DNSname → addressInternet providerLoad balancertraffic −8%Serversall greenServer monitor
SECTION 01 OF 2

1. Focus on Client-Side Errors in a Monitoring System

★ FREE PREVIEW
Key Takeaway: Server-side monitors observe only traffic that arrives at the ingress load balancer; failures in DNS resolution, ISP routing, CDN edges, TLS handshakes, or client runtimes drop users silently and require external measurement.
ARCHITECTURE / DATA FLOW DIAGRAM
your site is downUsersregion Aexpired record?DNSname → addressInternet providerLoad balancertraffic −8%Serversall greenServer monitor

The 'Green Dashboard' Outage Paradox

Every user interaction originates on a client device, resolves the service domain via DNS, traverses a residential or cellular ISP and intermediate BGP transit networks, negotiates TLS at a CDN edge, and only then arrives at the origin Load Balancer. Server-side telemetry observes exclusively from the load balancer inward. Suppose a major regional ISP pushes a bad BGP route that blackholes packets destined for our service IP: affected users suffer 100% connection timeouts, yet 0 error responses are logged by our servers. Internal dashboards show 0.00% HTTP 5xx errors, fast p99 latency, and a modest dip in global RPS easily mistaken for normal off-peak diurnal variance.

  • Survivorship Bias in Server Logs: Backend metrics measure errors / arrived_requests, completely ignoring dropped_requests that never reached the VIP.
  • User-Centric Availability: Customers experience end-to-end availability across DNS, ISP, CDN, TLS, and UI rendering—regardless of whether our backend fleet caused the fault.

Taxonomy of Pre-Ingress and Client-Runtime Failures

Failures invisible to backend application servers cluster into five distinct layers along the client-to-edge path and inside the client execution sandbox itself.

Failure LayerConcrete Production ExamplesWhat Server-Side Monitoring Sees
DNS ResolutionExpired domain registration, broken CNAME, authoritative DNS DDoS, NXDOMAIN/SERVFAILGradual traffic drop as DNS TTLs expire globally; 0 server errors
ISP & BGP TransitRegional carrier packet loss, BGP route leak/hijack, submarine fiber cut, carrier firewall blockAbrupt traffic drop from specific GeoIP/ASN cohorts; 0 server errors
CDN & Edge WAFMisconfigured WAF rule returning 403, wedged PoP proxy, corrupt cached JS assetReduced origin cache-miss fetches; origin health checks stay 200 OK
TLS & CertificatesExpired TLS leaf cert, missing intermediate CA on older Android devices, clock-skew cert rejectionTCP SYN/ACK completes at edge, TLS alert aborts before HTTP layer logs
Client Runtime (Web/App)Uncaught JS TypeError white-screening React root, CORS preflight block, mobile OOM/ANR crashInitial HTML/API returned 200 OK; subsequent user funnel clicks vanish

Bridging Both Halves of Observability

Because server-side telemetry excels at pinpointing internal microservice, database, and host bottlenecks while remaining blind to external reachability, production observability requires fusing both perspectives. Correlating server-side RPS dips against client-side regional error spikes lets on-call engineers distinguish a benign quiet evening from an ISP outage or broken JavaScript release within 60 seconds.

Interview Signal: In interviews, pair client-side error collection with server-side 'traffic drop' anomaly detection (comparing live RPS per country/ASN against a 7-day seasonal baseline) as an immediate secondary signal when external networks sever client reporting.
SECTION 02 OF 2

2. Design of a Client-Side Monitoring System

🔒 PRO SECTION
Key Takeaway: Combine 1-minute global Synthetic Probes for a deterministic 24/7 baseline with 1%-sampled Real User Monitoring (RUM + W3C NEL) routed over a strictly isolated out-of-band collector domain for last-mile ASN coverage.

Section 1 + Checkpoint Quiz #1 are unlocked free outside the paywall. Unlock all architecture slides, QPS & sharding trade-off tables, and all 80 narrated HD video lessons with Full Access — or inspect our sample payment system lesson first.

ACTIVE RECALL & TRADE-OFF PROBES

System Design Checkpoint Quizzes (1)

CHECKPOINT QUIZ #1

In "Focus on Client-Side Errors in a Monitoring System" (Taxonomy of Pre-Ingress and Client-Runtime Failures), how does a production-grade design handle "ISP & BGP Transit" (What Server-Side Monitoring Sees)?