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

Event flow monitoring #715

Merged
merged 4 commits into from
Jan 11, 2024
Merged

Event flow monitoring #715

merged 4 commits into from
Jan 11, 2024

Conversation

scholtzan
Copy link
Contributor

Depends on mozilla/bigquery-etl#4744

Checklist for reviewer:

When adding a new derived dataset:

  • Ensure that the data is not available already (fully or partially) and recommend extending an existing dataset in favor of creating new ones. Data may be available in bigquery-etl repository, looker-hub or in looker-spoke-default.
  • Avoid merging a PR that includes the logic of a core metric or complex business logic. The recommendation is to implement core business logic in bigquery-etl. E.g. The type of search or the calculation of DAU or visited URIs.
  • Avoid merging code in Looker Explores/Views that implement analysis with multiple lines of code or that will be likely replicated in the future. Instead, aim for extending an existing dataset to include the required logic, and use Looker aggregates to facilitate the analysis.
  • Avoid merging a PR with logic that requires validation and health checks. It is recommended to implement it in bigquery-etl for full test coverage and failure alerts.

@scholtzan scholtzan requested a review from akkomar January 5, 2024 00:28
@scholtzan scholtzan merged commit ece1610 into main Jan 11, 2024
@scholtzan scholtzan deleted the event_flow_monitoring branch January 11, 2024 20:12
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.

2 participants