Hey @gaprl !

Do I get this right: we get ok check-ins for check-ins that we never sent a in_progress check-in?

Can we check on the server if the in_progress check-ins have been received but have been discarded for some reason (like because they are in a wrong format?)

I think the best way to track this down would probably to start by having some mode where the sentry SDK logs when it sends in_progress and when it sends oks, do we have anything like that yet?

if you set debug=True you will see that there has been an envelope of type monitor sent (which is a check-in) but you can not see if it is ok/ in_progress…
But I guess this would be a nice debug output to have.

Hey @gaprl I now checked the client outcomes in the admin interface and it seems that every once in a while the server is dropping check-ins (here on May 16th there where 16 check-ins dropped):

Can we somehow find out why those where dropped and what check-ins those where?

Another thing that jumped into my eye is that the monitors-detect-broken-monitor-envs are all very short lived tasks (sometimes only 100ms long). We had a problem before where check ins where processed in the wrong order. Could this also be happening here due to the in_progress and the ok checking landing in different queues and thus the ok is processed before the in_progress?