OTCA study guide
OTCA · Work through your exam, one topic at a time.
The OpenTelemetry Certified Associate (OTCA) is a multiple-choice credential for engineers who work with OpenTelemetry, the vendor-neutral framework for generating, collecting, and exporting telemetry. It suits SREs, platform and DevOps engineers, backend developers, and observability specialists who instrument services, run a Collector, or maintain telemetry pipelines. The OTCA study guide has 6 sections and about 1,844 words.
01OpenTelemetry Fundamentals and Concepts
OpenTelemetry (OTel) is a vendor-neutral, open-source framework for generating, collecting, and exporting telemetry. Its core purpose is to standardize how telemetry is produced and shipped, while deliberately leaving the backend (storage, query, visualization) out of scope.
328 words, about 2 min02Signals: Traces, Metrics, Logs, and Baggage
Each signal has distinct semantics and pitfalls. Traces model request flow.
300 words, about 2 min03Instrumentation (Automatic and Manual)
Automatic (zero-code) instrumentation injects telemetry without source changes, typically via an agent, language-specific init hooks (e.g., -javaagent , auto-instrumentation packages, eBPF), and produces spans for common libraries (HTTP clients, DB drivers, frameworks). Manual instrumentation uses the API directly to create spans, metrics, and log records for business logic that auto-instrumentation cannot see.
295 words, about 1 min04Collector Architecture and Configuration
The Collector is a vendor-neutral binary that receives, processes, and exports telemetry. Its config is a YAML file organized by pipelines , each composed of three component types: receivers (ingress, e.g., OTLP, Prometheus, filelog), processors (transform/filter/batch/memory-limit), and exporters (egress to a backend or another collector).
295 words, about 1 min05Context Propagation and Semantic Conventions
Context propagation carries trace context (trace ID, span ID, flags) and baggage across process boundaries. Two parts: in-process context (how the active span is stored/retrieved, e.g., thread-local or async context) and cross-process propagation via propagators that inject/extract context into carriers like HTTP headers.
304 words, about 2 min06Deployment, Operations, and Troubleshooting
Operational success depends on configuration hygiene, resource limits, and knowing where telemetry can silently drop. Deployment: choose agent vs.
322 words, about 2 min