Closed Bug 1184082 Opened 9 years ago Closed 9 years ago

Verify the send logic didnt break submission behavior

Categories

(Toolkit :: Telemetry, defect, P2)

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox42 --- affected

People

(Reporter: gfritzsche, Unassigned)

References

Details

(Whiteboard: [unifiedTelemetry] [data-validation])

We need to verify that the send logic changes in bug 1156712 didn't break ping submissions.
I think we mostly need to look at the submission volume pattern over time here.

A monitor like this might answer most of this question, but doesn't actually render data further back:
https://pipeline-prototype-cep.prod.mozaws.net/#sandboxes/PrototypeSandbox-kparlante_ByChannelHour/outputs/PrototypeSandbox-kparlante_ByChannelHour.nightly.cbuf
Katie, can you look into this?
Flags: needinfo?(kparlante)
It would also be good to look at the "lag time" development (i.e. average/... time from ping creation to submission) to verify that
* we didn't regress it
* we actually improved it
Mark pointed me to this too:
http://ec2-50-112-66-71.us-west-2.compute.amazonaws.com:4352/#sandboxes/TelemetryChannelMetrics60DaysAggregator/outputs/TelemetryChannelMetrics60DaysAggregator.nightly.cbuf

From a quick first look, this seems sane - note that per mark, the drop after Jul 13 is expected for other reasons.
The first spike is probably catching up on "all the backlogged pings", then things normalize a bit.
The less even distribution is expected from my side (as we submit much more agressively/immediately).

However, i don't think i can judge things properly this week, so i'd love more eyes on this.
(In reply to Georg Fritzsche [:gfritzsche] [away jul 13-17] from comment #3)
> From a quick first look, this seems sane - note that per mark, the drop
> after Jul 13 is expected for other reasons.
See Bug 1172996 for the reason for the drop.
to Katie, moving to [40b9]
Priority: -- → P2
Whiteboard: [b5] [unifiedTelemetry] [data-validation] → [40b9] [unifiedTelemetry] [data-validation]
Thanks Katie, that is great.
This seems to go fine from a quick look, anyone else notice something suspicious?
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Whiteboard: [40b9] [unifiedTelemetry] [data-validation] → [unifiedTelemetry] [data-validation]
You need to log in before you can comment on or make changes to this bug.