From the In-flight: the money moving through your Kafka architecture map
A console redrive reaches Kafka through one server-side write check
The Redrive button posts to /api/redrive (Redrive.tsx:63-64, Api.java:136-147). ConsoleAuth asks for a token only when bound beyond localhost (ConsoleAuth.java:27,51). Setup.redrive refuses a queue the catalog does not own, try mode, and a real run unless the running profile has allowWrites (Setup.java:324-334). Redrive then writes each match back through a Kafka producer, rate-limited (Redrive.java:115,201-214). The disabled button is cosmetic; Setup is the guard.
Impact: Whether a click becomes a production write depends on one flag on the saved profile, checked in exactly one place.
Guards in order: console token (only beyond localhost), confirm dialog and canWrite in the browser (Redrive.tsx:86-116, Engine.java:360), dlq must belong to the catalog, not try mode, profile allowWrites, perSecond default 50 capped at 5000 and optional limit (Redrive.java:67-73), error/order/time filters (Redrive.java:249-260). Dry run defaults on when dryRun is absent (Api.java:145).
The trail
- Operator
- Console
- In Flight server and engine
- Observe, Connect and Serve Runtime
- Console Auth
- Console API
- Setup Actions and Causes
- Redrive
- Broker SPI
- Kafka Adapter
- Kafka cluster