We have evidence server side of UKM submitting duplicate entries (upload is identical). We should investigate under what conditions this could be occuring.
This could happen naturally if the client fails to see the collector gets the message, but the 200 response was lost. There is no way to completely eliminate that issue.
However, we are seeing some duplication with a very high volume, e.g. single records resent hundreds of times. That seems like it would require the client to be stuck in some kind of bad state.
One possible utility here would be to attach a Message with data about the current session {e.g. how many times has client tried to send this report, and what the last error was} to each Report Message in HTTP header, so that we could use that in debugging.
Comment 1 by rkaplow@chromium.org
, Sep 18 2017