Skip to content
Fluxify

observability See every block of every slow request.

A visual backend is only as good as its debugging story. Fluxify traces a route block by block, keeps every failed run, and sends it all to the tools you already use.

Read the docs
span · block name 0 ms 3.4 ms GET /users/:id route 3.4 ms Entrypoint entrypoint 0.04 ms Cache lookup kv_operations 0.35 ms Cache hit? if 0.02 ms Load user db_getsingle 2.4 ms Cache write kv_operations 0.3 ms Reply response 0.04 ms
Turn tracing on per route and every block records a span with its name, type, input and outcome. Spans export to your OpenTelemetry destination after the response, never in its way. Timings shown are illustrative.

sampling

Keep every failure. Sample the rest.

Tracing is switched on per route, because detail has a cost. What's exported is decided after each run ends: failed runs are always kept, successful ones are sampled.

finished runs → tail sampler after the run ends exported failed — always kept succeeded — sampled
Decided after a run finishes: failures are always kept, successes are sampled. Normal traffic stays affordable and you never lose the runs you need to debug.

destinations

Your stack, not ours.

Logs, traces and metrics each get their own destination: Loki for logs, any OpenTelemetry collector for all three. Telemetry leaves the worker off the request path, so a slow collector never slows a caller.

Worker your routes & workflows Logs Console Log · Cloud Logs · logger Traces per-route, a span per block Metrics request counts & durations Loki logs OpenTelemetry (OTLP) logs · traces · metrics Server console logs, when nothing is set
Pick a destination per signal in project settings. Unset traces and metrics aren't exported; unset logs go to the server console.

in the editor

Logs where you can find them.

Logging blocks and the script logger write to the project's log destination. Compile errors and other system events show up in the editor next to the route they belong to.

  • Console Log

    print to the server logs from any point in a flow

  • Cloud Logs

    ship a line straight to Loki or OTLP

  • Per-route tracing

    on for the routes you're watching, off for the hot ones

  • Compile status

    a failed save is reported on the route, with the reason

next Integrations Databases, key-value stores, queues, log sinks and AI models.