← All games

Telemetry Contract & Instrumentation Lab

Build trustworthy Spring telemetry contracts with explicit ownership, bounded cardinality, and evidence-quality checks.

Concept
Observability & SRE Operations
Difficulty
Advanced
Play time
9-11 minutes
Path
Observability & SRE Operations

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 Contract & Instrumentation Lab is focused practice for Observability & SRE Operations. It explains why each answer is safe, risky, or production-ready.

Build telemetry that remains trustworthy as services, conventions, and exporters evolve.

Learning objectives

  • Assign instrumentation and exporter ownership.
  • Keep metric cardinality bounded while preserving trace context.
  • Evolve semantic conventions without losing alert continuity.

How to play

  1. Inspect the telemetry boundary and evidence.
  2. Choose or order every defensible action.
  3. Review why unsafe options corrupt evidence.

Scoring

  • Each correct scenario adds 250 points.
  • Missed decisions enter local review.
  • A perfect session scores 1,250.

Backend concept notes

Instrumentation is a contract between application semantics, context propagation, export, and analysis.

The game rewards bounded dimensions, compatible evolution, and explicit evidence limits.

Common mistakes

  • Duplicating automatic and manual instrumentation.
  • Putting request identity into metric labels.
  • Treating incomplete telemetry as conclusive evidence.

Review misses from this game

Related Backend Study Lab tools

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

FAQ

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

Does this game send real telemetry?

No. Every scenario is deterministic and remains in your browser.

Should every request field become a metric attribute?

No. Metrics need bounded dimensions; request-specific context usually belongs on traces or protected logs.

Leaderboard

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

Loading leaderboard...

    Finish the game to load your latest local score.