Closed
Bug 1534354
Opened 6 years ago
Closed 6 years ago
Validate telemetry on the new data pipeline
Categories
(Firefox :: New Tab Page, enhancement, P2)
Firefox
New Tab Page
Tracking
()
RESOLVED
FIXED
People
(Reporter: nanj, Assigned: nanj)
References
(Blocks 1 open bug)
Details
Now that we have telemetry mirroring enabled in all pre-release channels, we'd like to verify following items:
- Total number of records in the impression table in BQ matches against the total number of records in the session table in RS. Note that on the RS side, we should only fetch sessions from those users who have Top Stories enabled in the beta and nightly channels.
- Total numbers of impressions/clicks/blocks/save_to_pocket match against the impression table in Redshift. Note that we store an array for impressions in the BQ table, whereas those impression arrays are splitted into individual impressions in Redshift.
- Verify that all the columns (both required and optional) are stored in BQ, and the values are expected.
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → najiang
Assignee | ||
Updated•6 years ago
|
Iteration: --- → 68.1 - Mar 18 - 31
Priority: -- → P1
Assignee | ||
Comment 1•6 years ago
|
||
Have finished up the first round validation, all the results have been recorded in the Tiles/GCP doc.
Will meet with data team to discuss the next steps.
Assignee | ||
Comment 2•6 years ago
|
||
Filed a bug for gcp-ingestion to track the issues that we found during the data validation.
Updated•6 years ago
|
Iteration: 68.1 - Mar 18 - 31 → 68.2 - Apr 1 - 14
Updated•6 years ago
|
Iteration: 68.2 - Apr 1 - 14 → ---
Priority: P1 → P2
status-firefox66:
--- → disabled
status-firefox67:
--- → disabled
status-firefox68:
--- → disabled
status-geckoview66:
--- → disabled
Comment 3•6 years ago
|
||
Reverting spam.
status-firefox66:
disabled → ---
status-firefox67:
disabled → ---
status-firefox68:
disabled → ---
status-geckoview66:
disabled → ---
Updated•6 years ago
|
Component: Activity Streams: Application Servers → New Tab Page
Assignee | ||
Comment 4•6 years ago
|
||
Close it as Kenny and I have verified the data in release 68. Everything looks good except a minor issue on the backend side, which has already been fixed here.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•