Skip to content

Learn OpenTelemetry by solving real engineering problems

Choose a starting point that matches your work. Our public guides explain concrete decisions and configurations; our courses organize the wider subject into a progressive curriculum.

Written and taught by Juraci Paixão Kröhling, OpenTelemetry maintainer and Telemetry Drops founder.

Build reliable Collector pipelines

For SREs and platform engineers configuring telemetry collection and routing.

Learn to distinguish telemetry quality problems from volume problems, then work through a severity-based routing configuration.

Continue with Collector modules covering OTTL, queues, WAL, authentication, TLS, connectors and scaling. Compare the course curricula.

Design telemetry contracts and instrumentation

For software engineers and teams standardizing instrumentation across services.

Use the Weaver guide to connect a versioned telemetry schema to generated code, then examine what preserving the OpenTelemetry data model means.

Continue with course modules on the data model, context propagation, API, SDK and manual instrumentation. Compare the course curricula.

Learn from the wider OpenTelemetry community

For engineers evaluating approaches and keeping their knowledge current.

Explore curated conference talks and the OTel Drops podcast, with technical articles available when you want a deeper explanation.

Continue with modules on architecture, migration and observability culture to connect implementation details to team decisions. Compare the course curricula.

What happens to queued telemetry on restart?

In-memory queue

Application

OTLP ↓

Collector

Exporter sending queue

RAM

OTLP ↓

Telemetry backend

Any unsent data remaining in RAM is lost when the Collector exits.

Persistent queue

Application

OTLP ↓

Collector

Exporter sending queue

Disk · file_storage

OTLP ↓

Telemetry backend

Queued data can survive a restart when its storage survives.

Conceptual queue comparison. Persistence requires a configured storage extension and surviving disk; it does not guarantee delivery through every failure. Read the Collector resiliency guidance.

Choose the support you need

The OpenTelemetry Collector course and OTel Track are self-paced. OTel Specialization is an eight-week cohort program with weekly mentoring and personalized project feedback; check the course pages for current enrollment, waitlist options and prices.

Preparing for OTCA?

Use our unofficial OTCA practice exam to check your understanding. The interactive quiz requires JavaScript. Completing a Telemetry Drops course does not award CNCF's OTCA credential.

Questions about learning paths

Can I learn before purchasing a course?

Yes. Our technical articles, OTTL cheatsheet, podcast, and independent OTCA practice exam are free resources. Paid courses provide a progressive curriculum, with mentoring and feedback in Specialization.

Read free OpenTelemetry articles

Where should I start with Collector pipelines or instrumentation?

Choose the Collector learning path for collection, routing, and OTTL. Choose telemetry contracts and instrumentation for Weaver, schema design, and the OpenTelemetry data model. Each path links to practical public guides.

How do the Telemetry Drops courses differ?

The OpenTelemetry Collector course is self-paced training on designing, building, and operating Collector pipelines, with hands-on labs and one year of access. OTel Track is broader self-paced training on OpenTelemetry with recorded lessons, practical exercises, and one year of access. OTel Specialization is an eight-week cohort program with weekly expert conversations and personalized project feedback.

Compare the course curricula

Does a course completion certificate award OTCA certification?

No. A Telemetry Drops completion certificate is separate from CNCF's OpenTelemetry Certified Associate (OTCA) credential. Our practice exam is independent preparation and does not award certification.