- Use normalized_channel instead of application.channel
- Remove date filter, use current_date instead
- this is b/c main_nightly only has 6 months of data
- Update doclines to clarify table use
This will most of the time just give us HTTP 429 - Too Many Requests anyway,
because the call came from within the house ... I mean network and
GitHub rate-limits that.
This migrates the existing Travis CI tasks using only GitHub-provided
GitHub Actions and some shell commands. It can't get more simple.
Builds run on pull-requests and pushes against the master branch.
Deploys only run against pushes to the master branch.
* Add docs that outline when and where we filter
* Add docs about querying the error stream
* Apply suggestions from code review
Co-authored-by: William Lachance <wrlach@gmail.com>
* Apply feedback from review
* Update spalling
Co-authored-by: William Lachance <wrlach@gmail.com>
Where possible this removes mentioning of Databricks as one way to do things.
It is kept in historical docs for ... history.
All links to Mozilla's Databricks have been removed as the instance is shut down.
* Sketch out some gotchas around build ids.
* Add some additional info to address feedback.
* Apply suggestions from code review
Co-authored-by: William Lachance <wlachance@mozilla.com>
* Spellcheck!
Co-authored-by: William Lachance <wlachance@mozilla.com>
* Adding in documentation for newly added user states fields, in addition to newly added updates to `clients_last_seen`.
* Resolving PR comments: spelling/grammar errors, adding additional link to user segments section, and additional description to `days_since_created_profile`.
* Resolving PR comments: spelling/grammar errors, adding additional link to user segments section, and additional description to `days_since_created_profile`.
Co-authored-by: Corey Dow-Hygelund <cdowhygelund@mozilla.com>
I will be shopping around this workflow to some Data Scientists for review.
It is intended to empower them to explore new feature usage definitions
in a manner that has a clear path to being included in clients_last_seen
if it proves useful.
Relevant to the [Data Warehouse daily aggregations sub-project](https://docs.google.com/document/d/1Lml-hWiqhvUazjn_-sDF6TUvwAEA3jMG3LJbyIC7fEc/edit#).
* Update for Fenix release
* Use 'ping tables' language
* Add some more product IDs; disambiguate app_name vs Glean dataset
* Clarify references to Firefox event ping
* Update prototype project docs to apply to data eng and include ops eval
* Update src/cookbooks/gcp-projects.md
Co-authored-by: William Lachance <wlachance@mozilla.com>
Co-authored-by: William Lachance <wlachance@mozilla.com>