Forensic tool to identify misoperation on DB

In case a buggy application that uses FDB deletes or changes the DB, the application owner may want to know which operation performs the misoperation and when.

A forensic tool that shows all mutations with timestamp will help answer the above questions.

The tool can be built on top of point-in-time restore system which has already parse the backup data and reply the mutations.

Start by reading the point-in-time restore system that parses backup data and replies with mutations. Define how a forensic tool could expose every mutation with its timestamp for investigating unintended database changes, then determine the relevant design and validation work; the issue names no files or tests.

Written by the indexing model from the issue text.