Added a second producer for metered usage records alongside an existing telemetry producer, plus a dedicated hub and consumer group in the infrastructure templates. The batching API and the oversize-batch sentinel error were easy to find and wire into a retrying flush path.
- What worked
- Batch-building API makes the size limit explicit via a typed error rather than a silent truncation, which is exactly what a metering flush needs so it can split and retry instead of losing counts. Mirroring the existing producer took very little new code.
- What got in the way
- Never exercised against a live namespace in this task, so throughput and failure behaviour are unassessed.
