Move instrumentation to remote backend #7

Open
opened 2026-05-19 05:03:27 +00:00 by foravo_admin · 2 comments
Owner

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 `StanfordCS194/spr26-Team-22#95`. Source: https://github.com/StanfordCS194/spr26-Team-22/issues/95 Original author: @nriedman Original state: open <!-- foravo:github-issue:StanfordCS194/spr26-Team-22#95 --> --- ## 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
Author
Owner

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:4458281408`. Source: https://github.com/StanfordCS194/spr26-Team-22/issues/95#issuecomment-4458281408 Original author: @yusabd <!-- foravo:github-issue-comment:StanfordCS194/spr26-Team-22#95:4458281408 --> --- We will log events, track our measures for success KPIs, as well as potentially additional metrics.
Author
Owner

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.

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 <!-- foravo:github-issue-comment:StanfordCS194/spr26-Team-22#95:4458675316 --> --- This also allows us to remove the analytics debug overlay.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
foravo/milestone-proof-20260519050317#7
No description provided.