Closed
Bug 1191410
Opened 10 years ago
Closed 10 years ago
Run query or analysis to find the scale of the subsessionLength==0 issue
Categories
(Toolkit :: Telemetry, defect)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox42 | --- | affected |
People
(Reporter: gfritzsche, Unassigned)
References
Details
(Whiteboard: [unifiedTelemetry] [data-validation])
Bug 1191257 shows we have daily subsession pings showing up with subsessionLength 0.
I can't figure out via Kibana what the distribution here is.
We need to see distributions for subsessionLength (or counts of subsessionLength==0 vs. subsessionLength>0) per ping reason to judge the scale of the issue here.
Flags: needinfo?(kparlante)
| Reporter | ||
Comment 1•10 years ago
|
||
I see from my own client history that this can happen with subsessionLength>0, but still pretty short (<10sec for me).
Maybe we should look at a distribution like [<0, ==0, 0<x<=10, 10<x<=60, >60].
Comment 2•10 years ago
|
||
Here's a kibana dashboard, filtering out saved-session. Let me know if you want any tweaks.
https://kibana.shared.us-west-2.prod.mozaws.net/#/dashboard/elasticsearch/Telemetry%20Subsession%20Length%20Distribution
Flags: needinfo?(kparlante)
| Reporter | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•