Bugzilla

Something I noticed when checking the distribution of values is that the max value in Telemetry was 2^32 and the max in Glean was 2^31. This is expected, documented, tested, and in fact we have [error reporting for when Glean saturates a `counter` metric](https://mozilla.github.io/glean/book/user/metrics/error-reporting.html).

Surly this much of a difference in possible maximum, spread over the reporting population, can account for all or at least most of the 8x?

Alas, not. It does [get us down to something closer to 6x, though](https://sql.telemetry.mozilla.org/queries/83793/source#207635).

I guess I shouldn't have expected so much given [only a max of 150 or so pings complained they'd saturated their `counter`s](https://sql.telemetry.mozilla.org/queries/83795/source).

Something I noticed when checking the distribution of values is that the max value in Telemetry was 2^32 and the max in Glean was 2^31. This is expected, documented, tested, and in fact we have [error reporting for when Glean saturates a `counter` metric](https://mozilla.github.io/glean/book/user/metrics/error-reporting.html).

Surly this much of a difference in possible maximum, spread over the reporting population, can account for all or at least most of the 8x?

Alas, not. It does [get us down to something closer to 6x, though](https://sql.telemetry.mozilla.org/queries/83793/source#207635).

I guess I shouldn't have expected so much given [only a max of 150 or so pings complained they'd saturated their `counter`s each day](https://sql.telemetry.mozilla.org/queries/83795/source).