Closed Bug 1485692 Opened 7 years ago Closed 6 years ago

Discuss and Define what "session" and "subsession" need to be to be useful

Categories

(Toolkit :: Telemetry, enhancement, P2)

Product:
Toolkit
Component:
Telemetry
Type:
enhancement
Points:
2

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox63 --- affected

People

(Reporter: chutten|PTO, Unassigned)

References

(Blocks 1 open bug)

Details

Session and subsessions currently are a little strange. For instance, bug 857874 shows that it includes time picking a profile. And bug 1204823 shows that TimeStamp has platform-dependent behaviour which results in "time while computer is asleep" being included in session lengths for some platforms and not others. We need to discuss with some data scientists whether this is a problem, how it should be documented, and if it should result in changes on the client.
See bug 1205985 which suggests maybe there was at one time a desire for a stable-across-sleep measurement of session lengths.
See Also: → 1205985
And bug 1204939 and bug 1205567 on the same topic.
See Also: → 1204939, 1205567
Points: --- → 2
Priority: -- → P2

Clearly the situation as it exists is fine for most uses because I'm the only one thinking about it.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.