We expect the first (and for the foreseeable future _only_) user of Origin Telemetry (Content Blocking) to have a list of origins that has about 2500 elements in it (the Disconnect list). We're going to have to support that. This bug will: * Take care of splitting the origins list if it is longer than 2046 elements in a way that is transparent to API consumers. * Also add in support for the meta-origin which is set to 1 if a consumer tries to record an unknown origin to a known metric more than 0 times. Might give it a value of "__OTHER__" or something, and reserve it for internal use. * Notify the "origin-telemetry-storage-limit-reached" topic when the number of encoded `prioData` items would reach or exceed the value in the `toolkit.telemetry.prioping.dataLimit` preference.
Bug 1539262 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We expect the first (and for the foreseeable future _only_) user of Origin Telemetry (Content Blocking) to have a list of origins that has about 2500 elements in it (the Disconnect list). We're going to have to support that. This bug will: * Take care of splitting the origins list if it is longer than 2046 elements in a way that is transparent to API consumers. * Also add in support for the meta-origin which is set to 1 if a consumer tries to record an unknown origin to a known metric more than 0 times. Might give it a value of `"__OTHER__"` or something, and reserve it for internal use. * Notify the "origin-telemetry-storage-limit-reached" topic when the number of encoded `prioData` items would reach or exceed the value in the `toolkit.telemetry.prioping.dataLimit` preference.