Currently we do not parse collector response. Collector response, although normally 200 OK for a batch of events, may also include additional event delivery statistics, such as:

{"acc":6,"rej":4,"efi":{"EventLevelThrottling":[0,1,2,4]}}

which means:

• accepted (processed) 6 events
• rejected 4 events
• extended failure indicator: EventLevelThrottling for events 0, 1, 2 and 4

Protocol details are rather scarce (collector team may share some of this). But at least we can try to parse the reported result and try to bubble it up to customer debug callback. Another possible destination is evt_stats event that can carry information about when the throttling is applied. This event can be subsequently forwarded to customer's tenant and to customer's Geneva subscription via 1DS Event Forwarder. Then aggregate metrics can be generated to measure how often SDK emits an event that is subject to collector-based throttling (out of ingestion quota).