init patch for redis_logger:template,logging logic might have some space... #361
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[Idea]
Since managing the data was critical for debugging in our project,I briefly write a code for showing "redis" activity information from one request.The information should include "what Key was used" or "what was the Value" or "how fast" or "which function used"..etc
[Further]
1,I really want "expire" information of the key.So might add this feature,which will be available when it was specified to do so( on settings.py).
2,Templates can be better
3,I couldn't use "inherit class and return new class" sort of logic,as in sql or cache,but "replacing a function" sort of logic as instanced StrictRedis wouldn't be shared on one request.I'm wondering there might be more better way than what I implemented.
4,Calling function information might be acquired in more sophisticated way.