The problem/use-case that the feature addresses
Logging of the important commands that have significant impact to the database could be helpful on troubleshooting issues, without checking clients input.
Description of the feature
We could have a config that controls which commands should be logged. We might also need rate limited mechanism since some commands cab be executed very frequently.
Alternatives you've considered
Instead of printing the log, we can also dump the logs in a file.
Additional information
N/A
Comment From: oranagra
seems to me that this is out of the scope of redis (a config which specifies what commands to log). this can be handled by a module though.
i suppose this need would some day be covered in some way by an auditing feature (ref #10957)