Playground
See the signal before you send it¶
Edit scenario YAML on the left; the chart shows the exact values Sonda will emit.
This is not a simulation — it is the real sonda-core engine compiled to WebAssembly,
so compile errors, operational aliases,
jitter, and defaults behave exactly like sonda run. Underlined numbers are
draggable — grab one and slide left or right to scrub the value and watch
the signal reshape live.
What you can try here¶
The editor completes from the schema
Press Ctrl+Space anywhere in the YAML — or just start typing a field name — and the
editor offers what the format allows at that point: entry fields inside a scenarios:
item, all fourteen generator type: values inside a generator: block, encoder and sink
types, and the two operators while.op accepts. Each suggestion carries its type and the
same one-line description the API docs use, because both are generated from the same Rust
types. The published schema is the same file, so your own
editor can do this on your own files.
Everything the metrics engine supports works in the playground: the
core generators, the
operational aliases (flap,
saturation, leak, degradation, steady, spike_event),
jitter, multi-scenario files with shared
defaults:, labels, and every encoder for the output
preview. Gaps and bursts appear as shaded bands on
the chart.
Histogram entries render as a bucket
heatmap — one row per bucket, cell intensity showing where each tick's
observations landed, so a mean_shift_per_sec degradation is visible as
mass drifting into higher buckets. Summary
entries render as quantile bands (p50 brightest, tail quantiles above). Try
the Latency histogram + quantiles preset.
Log entries render as a synthetic
log stream — template messages resolved from their field pools, severity
colored, timed on the scenario timeline — with the json_lines output in the
encoded preview. Try the Synthetic log stream preset. One thing does not
run in a browser sandbox: csv_replay (metric or log) needs the filesystem —
use sonda new --from locally.
When the shape looks right, Test an alert → carries the scenario into the
alert lab so you can tune a threshold + for: rule against
this exact signal — and the same YAML runs unchanged with
sonda run or straight against a
real backend.