Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: is a custom LOGGING_JSON_ENCODER possible to use for an encryption requirement #40

Open
KIC opened this issue Sep 20, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@KIC
Copy link

KIC commented Sep 20, 2023

There are some sensitive data that would need to be encrypted before being stored to disk. Now I am wondering if I could use a custom LOGGING_JSON_ENCODER. But by looking at the code this is really only for encoding and not decoding. And I would need to decode an encrypted json.

EDIT: Alternatively I would also be happy if we could log into a very different database, like this comment suggests was an Idea once:

# TODO: Is not completed feature, do not use it!
#  It will prevent error in database if User is not in the same database (because of ForeignKey)
LOGGING_DATABASE = getattr(settings, 'LOGGING_DATABASE', 'default')
@legion-an
Copy link
Owner

Hello @KIC , I will try to implement LOGGING_JSON_DECODER in the near future, but to be able to put logs in another database, I think it will be a pretty big feature, not sure I will have time for it :(

@legion-an legion-an added the enhancement New feature or request label Sep 27, 2023
@creyD
Copy link
Collaborator

creyD commented Sep 28, 2023

@KIC if you want to implement it yourself, (please correct me if I am wrong @legion-an) we would be ready to review a PR and merge it pretty quickly.

@legion-an
Copy link
Owner

legion-an commented Sep 28, 2023

yes, of course, you are more than welcome @KIC :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants