Introduction to OpenTelemetry
Duration: 3 days (09:00 – 16:00 CET/CEST)
Participants: Max. 8 people
Format: Online or on-site
Language: German (English on request)
Certificate: ayedo certificate of attendance
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































Workshop overview
Duration, per-participant price and logistics for Introduction to OpenTelemetry.
Introduction to OpenTelemetry
Duration: 3 days (09:00 – 16:00 CET/CEST)
Participants: Max. 8 people
Format: Online or on-site
Language: German (English on request)
Certificate: ayedo certificate of attendance
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
Day 2: Process and protect telemetry in Kubernetes
Day 3: Visualise signals and resolve incidents end to end
Workshop schedule
Published daily rhythm. Topics are listed in the curriculum.
09:00–16:00 (CET/CEST)
Official window for open sessions.
09:00 – Introductions
On day 1: meet the instructor and participants, plus the agenda and workshop structure.
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).
Content blocks follow the curriculum
Theory and hands-on in the morning and afternoon blocks. The topic list is in the curriculum above.
12:00–13:00 – Lunch
A shared break before the afternoon.
16:00–16:30 – Q&A
End of the day: questions, exchange and wrap-up.
Prerequisites
What participants should bring.
Hardware
Your own notebook (Linux, macOS or Windows) with permission to install software. Devices available at extra cost.
Environment
Each participant works in a provided cloud lab. Local installation of the training stack is not required.
Prerequisites
Basic Linux/terminal skills are helpful.
Related workshops
Suggested follow-on courses from the catalog.
Kubernetes Monitoring
Duration: 4 days
Introduction to Istio
Duration: 3 days