OpenTelemetry Certified Associate (OTCA)
A vendor-neutral, associate-level certification covering the OpenTelemetry API and SDK, the Collector, context propagation, and debugging telemetry pipelines — with nearly half the marks on the SDK.
- src
- Linux Foundation Training & Certification — OpenTelemetry Certified Associate (OTCA) certification page (training.linuxfoundation.org)
- chk
The OTCA is the exam that tests whether you can produce telemetry, not whether you can query it. That distinction matters, because it is the one most candidates get wrong when they book it.
Where the marks actually are
Nearly half the exam — 46% — is the OpenTelemetry API and SDK. Not the concept of a span, but the data model, the configuration, the pipeline of processors and exporters, and how context crosses a process boundary. The Collector adds another 26%. Between them, 72% of the marks sit on things you build and configure.
Fundamentals of Observability is only 18%, and it is the part everyone over-prepares because it is the part that reads easily.
The practical consequence: someone who runs OpenTelemetry today through an auto-instrumentation agent and a Collector installed by a Helm chart has hands-on experience of maybe a quarter of this exam. The agent hides the SDK, which is precisely what is being tested.
What it is actually good for
Portability. OpenTelemetry is now the vendor-neutral layer beneath most commercial observability platforms, so the knowledge survives your employer changing vendor — which is the most likely disruption to an observability skill set, and the one a vendor certification does not protect you from.
The badge is a weak signal on its own. It is associate-level, multiple-choice, and there is no live environment anywhere in it. It proves you read the specification carefully. That is worth something, and it is not the same as having run a Collector fleet under load.
Against the Prometheus certification
These two are complements rather than alternatives, and the domain weights show it plainly. The PCA is weighted toward PromQL — querying data that already exists. The OTCA is weighted toward the SDK and the Collector — producing that data and moving it. If you are choosing one, choose by which half of the pipeline you are weakest in, not by which tool your employer runs.
Before you book
Instrument something by hand. One service, one language, all three signals, wired without an agent. It is the single highest-return preparation for an exam this heavily weighted toward the SDK.
75% is the bar, applied across the Linux Foundation's multiple-choice exams rather than published per exam. The question count is not disclosed for the OTCA.
$250 with a retake included, valid two years. Renewal means sitting the current exam again before it expires; there is no continuing-education route.
New to Linux and the command line?
This path assumes fundamentals you may not have yet. Our Foundations Pack is out and free — Linux, the shell and Git, with exercises that mark your work and explain why you got it wrong. We're writing an agents pack next; leave your email if you want to hear when it ships.
One email when the pack launches. No spam, unsubscribe any time.
Exam domains
The OpenTelemetry API and SDK
46%The OpenTelemetry Collector
26%Fundamentals of Observability
18%Maintaining and Debugging Observability Pipelines
10%Preparation path
- 1
Read the observability primer and the signals model first
Traces, metrics, logs, spans and baggage, and what OpenTelemetry means by each. This is vocabulary the rest of the exam assumes, and it is the cheapest domain to secure — the definitions are short, published free, and asked about literally.
~5 hours - 2
Instrument a real service with the SDK — this is 46% of the exam
Pick one language, add the SDK by hand rather than through an agent, and emit all three signals. Nearly half the marks live here, and it is the only domain you cannot pass by reading. Wire the pipeline yourself: exporters, processors, samplers and resource attributes.
~25 hours - 3
Run a Collector and change its configuration until it breaks
Receivers, processors, exporters and connectors, and the pipeline that joins them. Deploy it as both an agent and a gateway, then scale it. A quarter of the exam is here and it rewards having edited the YAML rather than having read about it.
~15 hours - 4
Break a pipeline on purpose and diagnose it
Drop a context header and watch a trace split in two. Misconfigure an exporter and find where the data went. The smallest domain at 10%, but it is the one that maps to the actual job, and the failures are quick to stage on the demo stack.
~8 hoursTroubleshooting the CollectorOpenTelemetry · FreeTelemetry schemasOpenTelemetry · FreeObservability EngineeringCharity Majors, Liz Fong-Jones, George Miranda, Austin Parker · Paid · aff — Affiliate link — we may earn a commission at no extra cost to you. A free alternative is always listed alongside.
Frequently asked questions
Career Roadmaps
- Observability Engineer RoadmapA path into observability as a craft of its own — wide events, signal correlation, telemetry cost, collector pipelines, high-cardinality analysis, continuous profiling, and running observability as a platform other teams consume.
- Site Reliability Engineer RoadmapA path from DevOps fundamentals into the specialized discipline of site reliability engineering, covering SLOs, observability, incident response, data reliability, and capacity planning.
- Platform Engineer RoadmapThe path DevOps engineers move into — building an internal developer platform as a product, covering Kubernetes as substrate, IaC at scale, GitOps, golden paths, portals, policy, multi-tenancy and adoption.