Collection pipeline / Reading notes
Delivery, duplicates and restarts
What a receiving service can safely assume.
State the guarantee
Describe when an event is acknowledged and what is persisted. Do not claim exactly-once delivery merely because events have identifiers.
Handle repeated batches
Keep event identifiers stable across retry attempts. Where duplicate suppression matters, define its retention window and scope at the receiver.
Observe collector health
Expose queue depth, oldest event age and rejected counts. These signals explain missing application events without pretending the collection path is always available.