OpenTelemetry

Card type mix

• multiple choice: 111
• true false: 73
• select blank: 37
• match pairs: 3
• order: 2
• multi select: 1
• code fill: 1

What's covered

1. What Observability Actually Means
2. The Signals: Traces, Metrics, Logs, and Profiles
3. Why OpenTelemetry Exists
4. Vendor-Neutral vs. Proprietary Agents
5. The API vs. SDK Separation
6. Instrumentation Libraries vs. Manual Instrumentation
7. Auto-Instrumentation, Briefly
8. What a Trace Actually Is
9. What a Span Represents
10. Span Attributes and Events
11. Span Kind
12. Parent-Child Span Relationships
13. Trace ID and Span ID
14. W3C Trace Context Propagation
15. Baggage: Carrying Business Context
16. Context Propagation Across Service Boundaries
17. Metrics: Counters, Gauges, and Histograms
18. Metric Aggregation Temporality
19. Structured Logs in OpenTelemetry
20. Correlating Logs, Traces, and Metrics
21. Resource Attributes
22. Semantic Conventions
23. The OpenTelemetry Protocol (OTLP)
24. Exporters: Where Telemetry Goes
25. The OpenTelemetry Collector, Briefly
26. Collector Pipelines: Receivers, Processors, Exporters
27. Common Collector Processors
28. Sampling: Why You Can't Keep Everything
29. Head-Based vs. Tail-Based Sampling
30. Deploying the Collector: Agent vs. Gateway Pattern
31. SDK Configuration: Samplers, Exporters, Resource Detectors
32. Instrumenting an HTTP Service
33. Instrumenting Database Calls
34. Propagating Context Across Async/Queue Boundaries
35. Continuous Profiling as a Fourth Signal
36. Choosing a Backend
37. Common Pitfalls
38. OpenTelemetry on Kubernetes

Example cards

Latest: Initial release — 38 decks, 266 cards, each pack with a preview card teaching the concept before its graded main card and practice cards.