Skip to main content
All of these are optional — the defaults are the shape you want in production. A malformed value never silently changes behavior: Cerulion warns and falls back to the documented default.

Logging

Node logs are worth one note of their own. A node runs as a loaded library with its own log dispatcher, so tracing::info! from your tick() goes to stderr while the host’s own logs go to stdout. The filter is RUST_LOG as captured when the graph started, an empty value means info, and RUST_LOG=off silences node-side logs entirely.
Do not install a global tracing subscriber inside node code — the framework installs one before your node runs, and a second install panics and fails the node load. Control output with RUST_LOG instead.

Networking

Recording and capture

Visualization

Live-run tuning

These affect how the live loop idles and how work is spread across cores. Reach for them when you are chasing latency, not before.

Build

CLI reference

The flags that override several of these variables.

Network a graph

What the network variables change in practice.