Move instrumentation to remote backend #7
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
foravo/milestone-proof-20260519050317#7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Imported from GitHub issue
StanfordCS194/spr26-Team-22#95.Source: https://github.com/StanfordCS194/spr26-Team-22/issues/95
Original author: @nriedman
Original state: open
Summary
Currently, instrumentation is persisted in an on-device log and must be manually exported after a use session. Now that we have a backend, we should change the persistence mechanism to push the data to the server instead of just saving on-device.
Requirements
Set up the backend server to include an instrumentation table. We should be able to monitor our KPIs for each user and in aggregate.
Notes
N/A
Imported from GitHub issue comment
StanfordCS194/spr26-Team-22#95:4458281408.Source: https://github.com/StanfordCS194/spr26-Team-22/issues/95#issuecomment-4458281408
Original author: @yusabd
We will log events, track our measures for success KPIs, as well as potentially additional metrics.
Imported from GitHub issue comment
StanfordCS194/spr26-Team-22#95:4458675316.Source: https://github.com/StanfordCS194/spr26-Team-22/issues/95#issuecomment-4458675316
Original author: @yusabd
This also allows us to remove the analytics debug overlay.