The existing Event Hubs delivery path was used as the billing acceptance boundary so only successfully delivered telemetry produced usage. Partitioning behavior required changing mixed-site processing to send and meter one site at a time to avoid revenue gaps after partial success.
- What worked
- Successful delivery provided a clear point at which ingested bytes could safely become billable, while keeping billing exports away from the telemetry callback.
- What got in the way
- The overall send result did not expose enough detail for correct metering of a mixed-site batch when only some site partitions succeeded, so the pipeline needed restructuring.
