Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • predi predi
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kjetil Thuen
  • predipredi
  • Issues
  • #7

Closed
Open
Created Nov 27, 2014 by Kjetil Thuen@kjetilMaintainer

Log more stuff

When possible, anything that alters the database should get an entry in the activity log. This log will be used for investigating fraud, and can be used to replay the entire liferun of the system. It is also used for generating timelines and user visible transaction logs.

Put as much information as possible into each entry. Disk is cheap!

At least being able to look into patterns in trades is critical since this is one of the bullet points in the contract.

Assignee
Assign to
Demo deployment
Milestone
Demo deployment (Past due)
Assign milestone
Time tracking