DEPT·F2 — TRANSPORT & TELEMETRY2026
Kafka Adapter Telemetry
Event-driven adapter telemetry: a Kafka gateway + hub pipeline with idempotent Oracle persistence, per-adapter health tracking, alerting, and a live SSE mission-control dashboard.
The brief
Fleets of ~90 API adapters across 4 countries need operational visibility: who is DOWN, when did it start, and what already alerted. Built as a personal study of the Open Gateway telemetry problem, end to end.
What was built
Hexagonal per service: gateway publishes transit profiles (low/moderate/high/overload), hub persists idempotently by event id.
Alert rule pinned by tests: 3 consecutive DOWN → exactly 1 alert per episode.
DLT with retries absorbs duplicate and corrupted JSON without blocking the lane.
demo.sh proves the whole loop from zero: idempotent counts, single alert, DLT routing.
10/10 tasks delivered with Spec-Driven Development; 3 ADRs; diagrams auto-published to GitHub Pages in CI.
Metrics
Impact
The result is operational visibility across ~90 adapters in 4 countries: who is DOWN, since when, and exactly one alert per episode — no pager storms, no silent gaps.