1956525 - Glean InvalidValue errors when recording to newly migrated `memory.vsize` metric

Status: NEW

(Core :: XPCOM, defect)

Description

[Travis Long [:travis_]]

Glean records an InvalidValue error when recording this metric. This currently affects about 50% of the Desktop nightly population, and errors started on March 22nd when this metric was first migrated.

Comment 1

[Travis Long [:travis_]]

GLAM records for the Legacy histogram data doesn't show any big changes in the last few weeks: https://glam.telemetry.mozilla.org/firefox/probe/memory_vsize/explore?channel=beta
The 95th and 75th percentiles shown for this in GLAM are both "17M", which makes me worry that a large portion of the recorded values are in the upper range of the data, which could indicate saturation at a cap or threshold and the InvalidValue errors would then likely be due to "> 1TB" rather than a negative being recorded.

At the very least, I don't think the Legacy instrumentation is gathering data at a resolution that's useful seeing as how it is capped at @17 MB (https://searchfox.org/mozilla-central/source/toolkit/components/telemetry/Histograms.json#1411) and a large portion of the data collected seems to be truncated at that cap.

If it is required that you need to record greater than 1TB samples, please do file a bug in Data Platform and Tools :: Glean SDK and we can address the limitations of the MemoryDistribution metric type and your specific needs.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:nika, could you have a look please?

For more information, please visit BugBot documentation.