Open Bug 1284860 Opened 9 years ago Updated 2 years ago

Have cleaner subsession semantics for child telemetry aggregation in the parent process

Categories

(Toolkit :: Telemetry, defect, P3)

Product:
Toolkit
Component:
Telemetry
Type:
defect

Tracking

()

People

(Reporter: chutten|PTO, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [measurement:client])

When bug 1218576 is done, it looks as though we'll be sending accumulations batched every 2s or so. This results in our subsessions having "fuzzy edges" where accumulations during one subsession could be applied to a subsequent subsession. 2 seconds' worth of fuzziness isn't the worst thing in the world, but we can do better. Prevailing idea at time of filing: * timestamp Accumulations on the child, * store a timestamp of the last subsession split on the parent, * use this information to ensure the current subsession hgrams only contain data accumulated during the current subsession.
Blocks: 1272003
Priority: -- → P3
Whiteboard: [measurement:client]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.