Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 1574490 - Add views for events. #510

Closed
wants to merge 30 commits into from
Closed

Bug 1574490 - Add views for events. #510

wants to merge 30 commits into from

Conversation

mreid-moz
Copy link
Contributor

These views are generated based on the json configuration files from telemetry-streaming.

I used this script to generate them.

Copy link
Collaborator

@fbertsch fbertsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @akkomar who will be working on this. A rough overview of this and the associated script look good, but we really need to compare these views to the data in Amplitude directly - I commented in the bug about that.

@relud
Copy link
Collaborator

relud commented Nov 21, 2019

I used this script to generate them.

we should include that script in this PR, probably as templates/telemetry/make_events_view.py

@akkomar
Copy link
Collaborator

akkomar commented Nov 22, 2019

I used this script to generate them.

we should include that script in this PR, probably as templates/telemetry/make_events_view.py

I have added it under templates/telemetry/make_events_view.py and adapted for this repo.

Some properties were hardcoded per ping type and not included in the
schemas
@akkomar
Copy link
Collaborator

akkomar commented Nov 27, 2019

I have exported Amplitude events from a single day corresponding to each mobile view and created notebooks to validate their correctness:

Mobile views look good - individual properties, total event count and grouped by name counts all match with the exports. We also have matching and stable insert_ids which makes backfills feasible.

Depending on next steps this is safe to merge at this point as devtools schema can be handled in a different PR.

It hasn't been used in legacy ETL and was a duplicate of `os`.
For consistency with Fenix view and new process
It duplicates event_type
akkomar added a commit to mozilla/telemetry-streaming that referenced this pull request Dec 2, 2019
…Amplitude job

This adds support to read from views introduced in mozilla/bigquery-etl#510.
This can be used as an alternative solution if S3 ingestion  takes too long to set up.
@akkomar
Copy link
Collaborator

akkomar commented Dec 17, 2019

Devtools schema is handled in #599

@akkomar
Copy link
Collaborator

akkomar commented Dec 30, 2019

This has been completed in #580 and #599.

@akkomar akkomar closed this Dec 30, 2019
@acmiyaguchi acmiyaguchi deleted the bug1574490 branch January 6, 2021 23:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants