Crate ferro_feed

Expand description

ferro-feed: high-performance crypto market data normalizer (multi-venue mode).

Usage: ferro-feed –config ./config.toml

The output is newline-delimited JSON (ndjson) by default, suitable for piping to downstream consumers.

Modules§

archive 🔒: md:v1 continuous archiver (#14) — the ferro-feed archive subcommand.
config 🔒: Runtime configuration for config-only multi-venue mode.
connector 🔒
control 🔒: Redis control-key watcher (#11).
metrics 🔒: Operational metrics: atomic counters, Prometheus HTTP endpoint, periodic stats logger.
model 🔒: Canonical market data types.
ohlcv 🔒: OHLCV bar aggregation from trade events.
sink 🔒
traits 🔒: Traits for exchange connectors and output sinks.
tui 🔒: Interactive ratatui dashboard for runtime monitoring.

create_connector 🔒
create_sink 🔒
init_tracing 🔒
main 🔒
parse_channels 🔒
parse_channels_strict 🔒
parse_symbol 🔒
resolve_env 🔒
run_fair_merger 🔒
spawn_task_panic_watcher 🔒
stream_end_is_fatal 🔒: #17 Phase-0 supervision contract: a PANIC in a supervised task (venue stream, fair-merger) exits the process so a process-level supervisor (systemd Restart=always / launchd KeepAlive) can restart it. Without this, a panicked task leaves the feed alive-but-wedged: the dead connector can’t update connected, so even /ready keeps reporting healthy. Clean task completion (e.g. stream end on shutdown) is NOT fatal.
validate_coinbase_funding_config 🔒
validate_ui_config 🔒
validate_venue_symbol_conventions 🔒
venues_supplying_bars 🔒: Venues that supply their own venue-aggregated bars (the aggregates channel) are excluded from the local trade aggregator, so the same venue never emits both venue bars and locally-aggregated bars. Gating is per-venue, so an aggregate venue can coexist with venues that do want local aggregation.