tidaldb/tidal/docs/planning/milestone-0/phase-2/task-02-metrics-surface.md
jx12n 3bcfb3c576 feat: Bazel build, crate docs/ai-lookup, docker images, and engine hardening
- Add BUILD.bazel across tidal, tidal-net, tidal-server, tidalctl for bzlmod build
- Add tidal/ crate docs (README, CHANGELOG, CONTRIBUTING, AGENTS, CLAUDE, API, ARCHITECTURE) and ai-lookup reference
- Add docker standalone/cluster/deploy images, compose, and prometheus config
- Harden WAL (batch format, writer, dedup, diagnostics), text syncer/collectors, and vector registry
- Expand tidalctl CLI and tests; restructure WAL/visibility integration test suites
- Refine tidal-net transport/client/server and tidal-server cluster/scatter-gather
2026-06-07 18:29:38 -06:00

725 B

Task 02 — Metrics / Health Surface

Goal: expose runtime stats (uptime, WAL lag, open handles) without requiring full observability stack.

Deliverables

  • Optional HTTP endpoint (disabled by default) serving /metrics (Prometheus text) and /healthz (JSON).
  • Builder flag enable_metrics(addr) + with_metrics(false) toggle for tests.
  • Metrics counters tagged with process, partition_id, build_hash for future distributed rollouts.

Acceptance Criteria

  • Endpoint can run on the same Tokio runtime as host service (returns Future implementor).
  • Minimal deps (hyper/tiny_http) to keep embeddable footprint light.
  • Integration test hits /metrics and asserts counters increment when WAL appends.