FLUENT BIT / EXPERIMENTAL

WASM test bench

Real C pipelines, running locally in browser workers. No external database or service.

Browser readiness

Live pipeline playground

Edit YAML, press Start, and watch real stdout in the output panel. Stop, adjust, and run again—no rebuild needed.

Auto-stop after seconds

Pipeline configuration (YAML)

Changes apply on the next Start. Max 64 KiB YAML and 300 seconds per run; shutdown grace is fixed at 1 second. Config stays in this page and a temporary browser filesystem, not on the server. The HTTP output sends records to its configured HTTPS destination. Only plugins in the browser build are available; no raw TCP/UDP outputs or TDA. Use threaded: false for event_type inputs. Browser Lua uses Lua 5.4, not LuaJIT: no jit, ffi, or native modules. Edit scripts inline with YAML code: |. Run only scripts you trust.

Live output

Ready

Start the demo or choose a test to begin.

Recovery touches only /storage/chunkio-regression. Use one test tab at a time. Do not reload or close this page during a run; an interrupted write may need recovery.

HTTP receiver — records delivered to this server

The HTTPS example uses a unique random URL on this test server. Captures stay in server memory for up to 10 minutes (last 20 requests, 8 KiB preview each; at most 16 capture URLs). Authorization values are not stored. Add ?fail=1 to the destination URL to test a 503 retry.

Load the HTTPS example to inspect delivered requests.

01 / PROCESSORS

YAML pipeline

Validate configuration and seven processors across logs, metrics, and traces.

02 / FILTERS

Filter pipeline

Modify and grep records, fan out to two outputs, then repeat engine startup and shutdown.

03 / PERSISTENCE

Local storage

Write ChunkIO files to IndexedDB, reload the test frame, recover them, and verify deletion.

YAML fixture and prototype limits

This read-only fixture is embedded when flb-wasm-yaml is built. The source shown below may be newer than your binary; rebuild after editing it.

Loading fixture…

The three acceptance-test buttons run fixed C tests; the playground above runs your edited YAML. Applications can use the browser SDK's push() API with a configured lib input. TDA is disabled pending a Ripser fix. The YAML test deliberately rejects malformed YAML, so an expected parser error appears in its log before the valid pipeline runs.

Storage uses a browser-local virtual filesystem, not a user-selected host directory. Only the storage test commits IndexedDB; the other tests use an ephemeral filesystem. Clearing site data removes persisted test files.