Closed
Bug 1400931
Opened 7 years ago
Closed 7 years ago
[meta] Add Direct-to-parquet for telemetry.error & telemetry.duplicates streams
Categories
(Data Platform and Tools :: General, enhancement, P3)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: frank, Unassigned)
References
Details
These two streams need not store the data in the ping, just some metadata about the ping - docType, appVersion, submissionDate, etc. It would make it easy for users to check if their pings are having problems, and would be accessible in re:dash.
Updated•7 years ago
|
Comment 1•7 years ago
|
||
Once the dependent bugs are resolved, we should have this info available in parquet.
We actually (kind of) already have this information in parquet form, but recent refactors have made it suboptimal.
Once the required changes are made we will have three parquet outputs:
mozingest_errors (for url-parsing failures)
telemetry_errors (for telemetry-specific failures)
telemetry_duplicates (for duplicate telemetry docids)
Priority: -- → P3
Summary: Add Direct-to-parquet for telemetry.error & telemetry.duplicates streams → [meta] Add Direct-to-parquet for telemetry.error & telemetry.duplicates streams
Comment 2•7 years ago
|
||
This should land on Monday.
Comment 3•7 years ago
|
||
These datasets are available via re:dash as telemetry_duplicates_parquet, telemetry_errors_parquet, and moz_ingest_uri_errors_parquet. Bug #1400935 is a separate but related concern so I've removed its blocking status and am closing this bug.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•2 years ago
|
Component: Pipeline Ingestion → General
You need to log in
before you can comment on or make changes to this bug.
Description
•