Backend Study Lab · Games
← All games

Telemetry Pipeline Builder

Build a bounded telemetry path for structured logs, trace context, sampling, batching, and safe attributes.

Concept
Telemetry pipelines and context propagation
Difficulty
Advanced
Play time
9-11 minutes
Path
Production Reliability

Interactive scenario

Playable game area: Make the next backend decision

Use the controls below. Feedback appears immediately and final scores stay in this browser.

Concept notes

Why this decision matters

Telemetry Pipeline Builder is focused practice for Telemetry pipelines and context propagation. It explains why each answer is safe, risky, or production-ready.

Carry useful, bounded evidence from instrumentation to the backend that operators query.

Learning objectives

  • Propagate context across synchronous and asynchronous boundaries.
  • Keep telemetry failure from blocking business traffic.
  • Control sampling, cardinality, and sensitive attributes.

How to play

  1. Follow evidence through each telemetry stage.
  2. Choose bounded and privacy-aware controls.
  3. Review what survives a backend outage.

Scoring

  • Correct pipeline controls add 250 points.
  • Lost or unsafe evidence enters local review.
  • A perfect pipeline scores 1,000.

Backend concept notes

Telemetry is a production data pipeline with capacity, privacy, and failure boundaries.

Correlation and semantic attributes make evidence joinable without duplicating raw payloads.

Common mistakes

  • Blocking requests on telemetry export.
  • Using unbounded attribute values.
  • Sampling away rare failures.

Review misses from this game

Related Backend Study Lab tools

Use tools from the main site when you want to inspect real inputs.

Keep practicing nearby backend concepts while the mental model is fresh.

Queues Intermediate

Message Queue Simulator

Tune workers, retries, and dead-letter behavior while jobs move through an async queue with failures and poison messages.

Time
7-11 minutes
Concept
Async jobs, retries, visibility timeout, and dead-letter queues
  • Production Reliability
  • Async Workflows
  • queues
  • retries
  • dead-letter queue
Play Message Queue Simulator
Reliability Intermediate

Observability Incident Triage

Triage production incidents by choosing useful metrics, logs, traces, queue signals, database evidence, request ids, and alerting strategies.

Time
6-9 minutes
Concept
Production observability, incident triage, metrics, logs, traces, and alerts
  • Production Reliability
  • observability
  • incidents
  • metrics
Play Observability Incident Triage
Observability Advanced

SLO Incident Commander

Direct incident response with RED, USE, service-level indicators, burn rates, and explicit recovery criteria.

Time
9-12 minutes
Concept
Service objectives and incident command
  • Production Reliability
  • Observability
  • SLO
  • Incidents
Play SLO Incident Commander

FAQ

Short answers for how this game fits backend interview and study practice.

Should telemetry export be synchronous?

Usually no. Use bounded asynchronous batching so observability outages do not become application outages.

Can correlation IDs replace trace context?

They help join records, but trace context also models parent-child relationships and distributed timing.

Leaderboard

Top 10 scores for the current ruleset. No account required.

Loading leaderboard...

    Finish the game to load your latest local score.