Diagnose realistic distributed tracing scenarios in a preloaded k3s VM, for users to get more familiar with traces in general and jaeger-ui specifically.

There's guided investigation through distributed traces, along with identification of slow spans and comparing two traces to identify what changed to make it slow down.

You can easily see trace duration and see which ones are taking longer than others.

You can also then see the individual spans in those traces

And it's really easy to compare traces via the Jaeger-UI "Compare" screen (not super nice on small screens yet, but I'm working on it!)

And you can even dig into the tags on the traces (you're tagging your traces, right?!?!) to see what changed since the span started slowing down