-
Notifications
You must be signed in to change notification settings - Fork 352
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
Add steps for local data ingestion in docs #7790
base: master
Are you sure you want to change the base?
Conversation
556eff6
to
e90500a
Compare
91638c9
to
84aa68e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work @sumairq :) just a few additional things we'll need to add to make it clearer for others.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for extending the documentation.
58c353f
to
19c6e33
Compare
@sumairq looking at the other documentation we have, and I'm wondering if it would make more sense to have this information on this page (maybe in the ingesting pushes section): https://treeherder.readthedocs.io/installation.html What do you think? |
Maybe we can keep the information under the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you.
docs/pulseload.md
Outdated
|
||
--- | ||
|
||
##### Run the following in separate window while running above to do ingestion |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @sumairq, sorry for the delayed review! In the image below, I noticed that this line is showing up as a new heading in the navigation list/bar on the right-hand side. Could you reformat this line to be in bold instead so it doesn't show up there?
I'm not sure about this, why do you think the |
Bug 1841022 - Add tests for the Debug Tools column in alerts view
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Bug 1827920 - also get the `updatePinnedJob` method in the local scope to fix sporadic push health issue The import was being used instead of the prop tied to the store resulting in the `updatePinnedJob` prop sometimes having the value of `null` when it is attempted to be called later inside FailureSummaryTab.
* Update Node.js to v20.6.1 --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Bug 1838836 - Add TaskclusterMetadata to the alert summary API endpoint
* Base the query on JobLog table * Filter from the database directly * Refactor the Python code * Add distinct clause * Force ordering of the entire payload * Add a comment for summarygroup result direct annotation
* Bug 1850785 - Allow for Marionette failures to be filed as single tracking bugs. r=aryx * allow mitten to work with cf jobs, fix bug with -cf at end of jobname.
Previously, select all checkboxes in the tests tab would always stay on the same position on screen due to a missing positive relative.
@sumairq would you be able to fix up this PR to only show the files modified by your PR? It looks like there are merge conflicts as well that need to be resolved. I think a forced push from an up-to-date branch could help. |
This PR updates the docs on steps to ingest data locally.
It is a solution for https://bugzilla.mozilla.org/show_bug.cgi?id=1850748