Log for All Syncs

[ashuchow]

The current way of tracking whether cards are being synced or not showcases a cascading set of notifications on the right side of the browser where for each card there is either a Success or Fail notification. These are unclickable and untrackable, making it difficult to navigate which cards were not synced properly.

The proposed solution to this would be - Record a log every time metabase manager is used to synchronise (the button is pressed). This would keep track of who triggered the sync and whether a sync failed, was a partial success or a complete success. There would also be a record and details for all cards that did not sync.

[Ashesh3]

This can be done in 3 phases :-

1. Adding a new Table for storing logs : - here first make a structure you want to have for the table which will be storing all records, column names, their types and the table name. [ This will go into prisma/schema.prisma file]

2. Writing database helper functions that store the data: [Refer to app/api/database/mapping/utils.ts for an example on how to interact with the database and store entries in a table using code], then create a new folder app/api/database/logging/utils.ts and write the equivalent logic there for adding a log entry / updating it when something changes, no need to add support for deleting a log.

3. Triggering this api call when the proceed button is pressed, and subsequently calling it again as and when the status changes (This can be discussed after step 1 and 2 are done), this involves making a fetch request to that newly added api endpoint. [ Example for api endpoint code app/api/database/mapping/route.ts , app/api.ts ]