-
Notifications
You must be signed in to change notification settings - Fork 17
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
Update analytics documentation #2130
Comments
Migrated from navapbc#131 (comment) @aplybeah - Not sure if it's bc I'm checking this out from the Project view side of things, but it's sorta tricky to tease out what I should be reviewing as new content. It'd be great if you could point to or include links... for example When I tried to check out the README.md - The history doesn't indicate any changes. Another example, when I tried to check out the Technical Overview & the Orchestration updates - the 1st link went to a 404 error. Is there possibly a draft version that I'm supposed to look at & guidance is provided in the PR version opposed to the Project view of the issue? |
I checked in with Billy and he thought this would land well in some of their Analytics improvement work so I've pushed it over to their Epic and will remove it from the Nava Sprint. |
Follow up PR: #3598 |
## Summary Fixes #2130 ### Time to review: __2 mins__ ## Changes proposed > What was added, updated, or removed in this PR. A few minor additions to the analytics documentation, as requested in the comments on PR #3562 ## Context for reviewers > Testing instructions, background context, more in-depth details of the implementation, and anything else you'd like to call out or ask reviewers. Explain how the changes were verified. ## Additional information > Screenshots, GIF demos, code examples or output to help show the changes working as expected.
Migrated from navapbc#131
Originally created by @acouch on Tue, 02 Jul 2024 14:29:08 GMT
Summary
The current analytics readme and docs focuses on the previous version of the tool. It should be rewritten to reflect the recent changes.
It should highlight the fact that we have moved to capturing analytics in a postgres analytics database that will house our future analytics data and that we will use Metabase as a analyses and dashboard tool. It should highlight that system is architected so that the analytics work that will be part of the project can be run locally, though it is housed in AWS.
Acceptance criteria
make start
1a. setup the github login or token 2. export the current datamake sprint-data-export && make issue-data-export
3. import the datamake sprint-db-data-import
and 4. view the data in metabase ie go to localhost:3100make
commands instead of the local poetry. The Github token thing might need to be included. Setting up the tool locally could be moved under that latter setting so it is clear it is just for the slack integration piece.make setup
doesn't exist AFIACT so should be removed.The text was updated successfully, but these errors were encountered: