#valkey #workflow #execution-engine #async

ff-observability

FlowFabric observability — OTEL metrics registry + typed handles + no-op shim

16 releases (breaking)

Uses new Rust 2024

new 0.15.0 May 3, 2026
0.13.0 May 1, 2026

#21 in #valkey

Download history 136/week @ 2026-04-19 379/week @ 2026-04-26

515 downloads per month
Used in 8 crates (6 directly)

Apache-2.0

35KB
384 lines

FlowFabric observability — OTEL metrics registry + typed handles.

This crate is the single place that touches OpenTelemetry / Prometheus. Consumers (ff-server, ff-engine, ff-scheduler) take an optional dep on ff-observability behind their own observability feature; enabling the consumer-feature transitively enables ff-observability/enabled.

Feature model

  • enabled off (default) — all types compile to zero-cost no-op shims. No OTEL / Prometheus crates in the dep tree. Call sites use the same Metrics::new() entry point as the real backend; every instrument method is a no-op.
  • enabled on — real OTEL MeterProvider + Prometheus exporter. Metrics::new() registers all instruments; Metrics::render returns the text-exposition body for /metrics.

Call sites under both features use identical call shape — that's the whole point of the indirection. If the shim ever grew a feature skew we'd lose the "same source compiles both ways" guarantee.

Dependencies

~0–21MB
~257K SLoC