Migrate glean-ac's `TimespansStorageEngine` data
Categories
(Data Platform and Tools :: Glean: SDK, task, P3)
Tracking
(Not tracked)
People
(Reporter: Dexter, Unassigned)
References
Details
(Whiteboard: [telemetry:glean-rs:m10])
This is like bug 1582102, but for a different engine.
|
Reporter | |
Updated•6 years ago
|
|
||
Comment 1•6 years ago
|
||
I went searching through the probe_scraper and the only TimespanMetricType I could find was the duration used by the baseline ping. Since this is a app lifetime metric, is there any point in building a migration storage engine for this type?
|
|
Reporter | |
Comment 2•6 years ago
|
||
(In reply to Travis Long from comment #1)
I went searching through the probe_scraper and the only
TimespanMetricTypeI could find was thedurationused by the baseline ping. Since this is a app lifetime metric, is there any point in building a migration storage engine for this type?
I think this is a great point. sync was planning on using these after we landed setRawNanos. However, that never happened. We'd need to check again all the metric types before releasing the glean-core binary to Maven anyway, we can always add this very quickly if needed.
Description
•