aim
aim copied to clipboard
Implement verbose logging in aim storage
trafficstars
Proposed refactoring or deprecation
Currently the logging on the storage module is sparse, non-informative and in some cases even misleading. Need to introduce verbose logging allowing to collect all the data about important (and time-consuming) operations performed. Examples of such operations are, opening/re-opening rocksdb Container indexing, etc.
Verbosity level can be set on CLI command via -v, -vv, -vvv options. On the SDK level, in can be a property of a Repo.
Motivation
Better understanding of how system performs in complex scenarios