Logging, error tracking and RUM + Tracing and OpenTelemetry for frontend
Comes up in: Debugging, Frontend system design, Hiring manager
This concept is being written. It gets the full five steps — explanation, predict, interview angle, practice with tests, and review cards. Here is exactly what it will cover, so you can study it elsewhere in the meantime.
What it covers
- client error tracking (Sentry-style: grouping, releases, source maps)
- structured logs
- session replay and its privacy risks
- RUM metrics
- alerting on error rate and vitals
- traces, spans, context propagation (
traceparent) - connecting frontend actions to backend traces
- sampling
Words you will know
What you will practise
- design alerts for a checkout page
- trace a slow click through the stack
Interview questions this answers
- How do you monitor a frontend in production?
- How do source maps work with error tracking?
- What are the privacy risks of session replay?
- How would you trace a slow user interaction to the backend?