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

Document what to look out for for new apps #543

Open
badboy opened this issue Jan 16, 2023 · 0 comments
Open

Document what to look out for for new apps #543

badboy opened this issue Jan 16, 2023 · 0 comments

Comments

@badboy
Copy link
Member

badboy commented Jan 16, 2023

With the recent treeherder addition I noticed that we don't really have good documentation around what happens for those new applications.

It should be all automated. But sometimes things break.
But how does a data engineer verify it worked?
How do they identify issues causes by the new product vs potential outside issues (that just got triggered by this)?
How to identify missing data because the CI task is missing vs missing data because of other failures?

It might be worthwhile to think about failure cases and document them.

User docs are here: https://mozilla.github.io/glean/book/user/adding-glean-to-your-project/enable-data-ingestion.html
We have generic gotchas documented here: https://github.com/mozilla/probe-scraper/blob/main/docs/common-failures.md

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

No branches or pull requests

1 participant