#34152 closed New feature (wontfix)
Add the ability to store logs in a table
Reported by: | Alireza Safari | Owned by: | Alireza Safari |
---|---|---|---|
Component: | Utilities | Version: | 4.1 |
Severity: | Normal | Keywords: | serilog, database-logging, log |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Hey there,
I think it'd be a great feature to be able to store logs in dedicated table to filter, and etc.. a lot easier what I have in mind is somthing like Serilog sinks (used for dotnet developers)
PS:
Serilog sink for PosgtresSQL: https://github.com/b00ted/serilog-sinks-postgresql
Change History (4)
comment:1 by , 2 years ago
Easy pickings: | set |
---|---|
Needs documentation: | set |
Needs tests: | set |
comment:2 by , 2 years ago
Owner: | changed from | to
---|
comment:3 by , 2 years ago
Easy pickings: | unset |
---|---|
Needs documentation: | unset |
Needs tests: | unset |
Resolution: | → wontfix |
Status: | assigned → closed |
comment:4 by , 2 years ago
You can use django-model-trackwr which allows you to know how and when a change happened. Also, it allows you to revert to a previous version of the object.
Note:
See TracTickets
for help on using tickets.
Thanks for this ticket, however it's already covered by 3rd party packages, e.g.
django-db-logger
. I'm not sure how usingserilog
is different because I've never used it (as probably most Python developers).Please first start a discussion on the DevelopersMailingList, where you'll reach a wider audience and see what other think, and follow the guidelines with regards to requesting features: