Introduction to OpenTelemetry
Workshop

A slow request crosses several services, but every service records something different. A dashboard may show the error without explaining where time was lost or which call broke the chain. OpenTelemetry provides shared APIs, conventions, and a transport protocol. It replaces neither the team's choice of useful data nor storage, querying, and visualisation in an observability system. The workshop is designed primarily for backend and application developers. Platform engineers, SREs, and DevOps engineers also benefit when they co-own instrumentation standards or Collector pipelines and can follo

Made in Germany ISO 27001 ISO 9001 DSGVO-konform DORA Compliant 24/7 Support
UDSVolkswagenLiebherrT-SystemsVendureecoConnextPortainerBITMARCKUelzener VersicherungenFJDDWTOCCReiner SCTCyrus IndustrialDGSIEMnanocosmosInheadenSplixSchwarzgruppeINHHadesHiOrg-Serverown3dTikfinityProgram51Buben & MädchenPrime InsightsTELTECElevantiqMoovitCFToolsStadt KölnVivavisAvemio

Workshop overview

Duration, per-participant price and logistics for Introduction to OpenTelemetry.

On-site options

  • Live online or on-site at your location

  • In-house: content, duration and focus can be tailored

  • Flexible dates, from 1 participant

  • German; English on request

  • Preconfigured cloud lab (also on-site)

  • Open groups: max. 8 people

  • Seat price same as online: €721.50 × days, excl. VAT

  • On-site in-house: individual quote (travel/logistics as incurred)

  • No published flat on-site surcharge

  • You provide the training room and internet

  • Open sessions: 09:00–16:00 (CET/CEST)

Curriculum

Topics by day at a glance.

Day 1: From application code to connected telemetry

  • Position OpenTelemetry in the Entire Data Path
  • Make Automatic Instrumentation Visible
  • Instrument Business Context Deliberately
  • Preserve Trace Context Across Services
  • Connect Traces, Metrics, and Logs
Day 1

Day 2: Process and protect telemetry in Kubernetes

  • Model Consistent and Efficient Telemetry
  • Bring Instrumented Services to Kubernetes
  • Choose Collector Topologies for Kubernetes
  • Build Three Signal Pipelines in the Collector
  • Enrich Kubernetes Context and Protect Data
Day 2

Day 3: Visualise signals and resolve incidents end to end

  • Connect Tempo, Prometheus, and Loki
  • Make Service Behaviour Visible in Grafana
  • Verify Trace Context Across Gateway and Mesh Boundaries
  • Detect and Limit Export Failures
  • Resolve a Complete Telemetry Incident
Day 3

Workshop schedule

Published daily rhythm. Topics are listed in the curriculum.

09:00–16:00 (CET/CEST)

Official window for open sessions.

Frame

09:00 – Introductions

On day 1: meet the instructor and participants, plus the agenda and workshop structure.

Day 1

09:00 – Q&A

On later days, resolve open questions from the previous day before the day's topics (usually 09:00–09:30 or 09:00–10:00).

Later days

Content blocks follow the curriculum

Theory and hands-on in the morning and afternoon blocks. The topic list is in the curriculum above.

Topics

12:00–13:00 – Lunch

A shared break before the afternoon.

Break

16:00–16:30 – Q&A

End of the day: questions, exchange and wrap-up.

Close

Prerequisites

What participants should bring.

Hardware

Your own notebook (Linux, macOS or Windows) with permission to install software. Devices available at extra cost.

HardwareNotebook

Environment

Each participant works in a provided cloud lab. Local installation of the training stack is not required.

LabCloud

Prerequisites

Basic Linux/terminal skills are helpful.

Prerequisites

Related workshops

Suggested follow-on courses from the catalog.

Kubernetes Monitoring

  • Duration: 4 days

Introduction to Istio

  • Duration: 3 days