Amsterdam JUG OTel Workshop at Dash0

Join in with the latest Amsterdam JUG Workshop at Dash0 (which is at Dash0, Nieuwezijds Voorburgwal 162/Suite 401, 1012SJ Amsterdam), in which we learn all the basic principles of OpenTelemetry, while eating pizza, (and celebrating Yoeri Krom's birthday). Important: Bring your own laptop because this is a hands-on workshop where you'll be learning about OpenTelemetry from scratch! On your laptop, you need a local Kubernetes cluster to already be running (e.g., kind or k3s). On your laptop, you need to have a Java, Node, .NET, Python or Ruby application that is important to you and that you know how to deploy on Kubernetes; if you don’t have one, we will have test applications available, but that would only be half the fun! Limited seats, exclusive workshop, sign up quick! Agenda 17:30 — Doors Open (and Food and Drinks) 18:00–18:20 — OpenTelemetry for Complete Beginners (Part 1). 18:20–18:50 — OpenTelemetry for Complete Beginners (Part 2). 18:50–19:20 — Hands on Lab 1: Instrumenting a demo app. 19:20–19:35 — Break. 19:35–20:10 — Hands on Lab 2: From data to answers. 20:10–20:40 — Hands on Lab 3: Break things on purpose. 20:40–21:00 — Wrap-up. Details on Labs Lab 1: Instrument a demo app. Add OpenTelemetry to a small service from scratch: SDK, auto-instrumentation, and a collector. You'll send the resulting traces, metrics, and logs into a demo environment so you can see what your instrumentation actually produces. Lab 2: From data to answers. With telemetry flowing, we'll work through real questions: which service is slow, why, and what changed. The environment that we set up in Lab 1 is our workbench, but the techniques (correlating traces with logs, reading resource attributes, querying by semantic conventions) apply to any OTel-compatible backend. Lab 3: Break things on purpose. Introduce latency, errors, and a misbehaving dependency into the demo app, while tracing the failure back to its cause using only what OTel gives you. The goal is to see how much of a real incident you can reconstruct from the signals, using the demo environment to check whether your diagnosis continues to makes sense.