Closed
Bug 1162637
Opened 11 years ago
Closed 9 years ago
Create landfill decoder
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P3)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: whd, Unassigned)
Details
Currently, decoding landfill for reprocessing requires hacking together bits of the edge decoder (for parsing the path) and the normal telemetry decoder. We should refactor common components for the edge and telemetry decoders into a module and create a separate landfill decoder that uses these same components.
I vaguely recall there being a little more nuance to this, but not specifically what the nuance was.
Updated•10 years ago
|
Priority: -- → P3
| Reporter | ||
Comment 1•10 years ago
|
||
https://github.com/mozilla-services/data-pipeline/compare/landfill_decoder?expand=1 is the munged decoder, for reference.
| Reporter | ||
Comment 2•9 years ago
|
||
We don't need this anymore with the new infra, where the submission is retained in landfill in a way that can be easily replayed using the regular decoder and the moztelemetry http output.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•