Skip to content
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

Audit trail #1612

Open
1 task done
mahalakshme opened this issue May 24, 2024 · 0 comments
Open
1 task done

Audit trail #1612

mahalakshme opened this issue May 24, 2024 · 0 comments
Labels

Comments

@mahalakshme
Copy link

mahalakshme commented May 24, 2024

Need:

  • Help in troubleshooting data problems
  • Many times when user report faulty data, since there is no audit trail it is almost impossible or takes signifcantly longer time to troubleshoot.
  • A simple audit trail like what Metabase and Freshdesk give would go a long way in supporting and using the product better.

Solution suggestions:

  • Have a audit record for each table where we just copy the row to the new audit table, before updating the main table

Inputs:

  • metadata(no need the QoS that we are providing may be - specific table)/transactional data(helps for losing data)
  • separate table - so current behavior not changed
  • triggers - before update - parallel table
  • single table - table_name, column_name, old_value, new_value, date_time
  • 3 approaches: single table, parallel table, json blob
  • Maintainenance: structure of table when source changing, features built on it
  • other tools: check out - easy to query, restore, SQL domain(spike)

Analysis:

Metadata tables: address_level, catchment_address_mapping, subject_type, encounter_type, program

Tasks

  1. petmongrels
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Analysis Review
Development

No branches or pull requests

1 participant