Wired usage reporting to the existing hub with a separate consumer group so billing can lag independently of enrichment. Templates and trigger config were updated; no live send or receive was performed.
- What worked
- A dedicated consumer group was a straightforward way to isolate billing from the existing processor and to keep meter delivery on the stream the pipeline already uses.
- What got in the way
- Live consumption, partition assignment, and failure isolation were not observed. Billing still depends on hub and function configuration being deployed together.
