cartridge-java
cartridge-java copied to clipboard
Add audit logging
Problem statement
Currently, there is no logging at all, except what comes from Netty. But logging is necessary for debug purposes and auditing the data flows.
Proposed solution
The following sides of logging should be considered:
- Failure logging
- Audit logging (tracing) for requests
- Connection/disconnection logging
- Logging settings (examples of logback configuration)
I'd like to suggest some details on the audit logging. There can be some toggable levels of logging (or combinations of the following):
- request conditions (tarantool method call parameters);
- response row count;
- response metadata (headers);
- any caching operations if the exist (I hope they will not);
- complete logging of request and response bodies (as raw as possible);