Build in logging - audit logging

Idea created by CarstenLevin on Jan 11, 2017
    Active
    Score22

    All major databases have build in logging functionality. This is needed in FileMaker ... for verification and trust.

     

    Audit logging

     

    Data in existing structure

    Minimum requirements

    For each file->table

    • Enable/disable logging per file or per table ... maybe not needed for the minimum logging
    • Logging of creation of record (timestamp, from account, from client IP, from application (webdirect, fmp, go etc),
    • Logging of deletion of record (timestamp, from account, from client IP, from application (webdirect, fmp, go etc),

     

    Optional/nice to have

    This is not unimportant, but would be a pleasure to have

    For each file->table

    • Enable/disable detailed logging ... absolutely needed for the detailed logging
    • Logging of change to data in ->table->Record->Field
      • timestamp, from account, from client IP, from application (webdirect, fmp, go etc)
      • changed [from] and [to]

     

    Logging does take performance. Detailed change logging does take up large amount of space. Thus the request for turn on/turn of, at least for the detailed logging.

     

    Considerations

    Logging going to external file, not within file.

    Logging format for phase 1/version 1 made with thought of future use (roll back/roll forward)

    I have on purpose not included changes to structure here ... it is an other issue.

    Should probably be done on the server side (also to be compatible with cwp, data api, webdirect etc.

     

    Questions

    What should be added