We zero fill null values and it's often confusing

[sentry-io[bot]]

Sentry Feedback: JAVASCRIPT-2QTG

the chart is empty but there was one data point

contact_email	[email protected]
name	Josh Ferge
source	new_feedback_envelope

[sentry-io[bot]]

Sentry issue: JAVASCRIPT-2RCF

[ale-cota]

Additional feedback from slack: zero-value and no-value are conflated in sentry (not just in metrics), and i think that is really unfortunate. it's a pretty visible graphing artifact when zooming into smaller timeranges, and here it is indistinguishable from the actual value going up and down. The only clue is that min() over 24h over the larger timeframe is only zero when the value is actually zero, but is larger than the smallest plotted value over 1h when there is no value. I suspect there are more issues this causes in aggregation, as a recent fix to timestamps in my instrumentation changed the avg() metric value significantly even though it shouldn't have.

so the above graph makes it look like there are zero-values (even the labels on hover tell me so), but when I zoom out and apply min(), I cannot find a zero-value anymore