Cloud Tracing Lab Playground
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.
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
A real VM, not a container
Get root on a VM with its own kernel, so Docker, Kubernetes, and systemd just work.
Read the docs →
SSH from browser or CLI
Use the built-in web terminal, or connect with labctl ssh, plain ssh, scp, or rsync.
Read the docs →
Drive it with AI
Let Claude, Codex, or any MCP client start this playground and run commands in it.
Read the docs →
Expose HTTP(S) ports
Give any web app running inside the VM a public URL - for yourself or to share with others.
Read the docs →
Share terminals
Invite others into your terminal session, or open it yourself from another device.
Read the docs →
Customize with init scripts
Add shell scripts that run at boot to install packages, clone repos, or seed test data.
Read the docs →
Private networking
VMs reach the internet via NAT with no public IP; several VMs share bridge networks.
Read the docs →
Ephemeral or persistent
By default, VMs are destroyed when the session ends; enable persistence to keep the disks for next time.
Read the docs →
Built-in container registry
A private registry.iximiuz.com for every playground to share images across services and VMs.
Read the docs →