Hi, Mukul
Never use a disk file for audit logging.
Use at least a DB. On the other hand, using logging facilities or
specialized tools are better options.
Jason's suggestion above might lead you to the right choice.
Kind Regards,
Sencer HAMARAT
On Mon, Jun 6, 2022 at 7:59 AM Mukul Verma
Hi Lalit,
Thanks for your reply.
Actually, It must cover all models. Not certain ones.
I thought middleware should be a much better place for this action, but I
can't imagine how to handle it.
Saygılarımla,
Sencer HAMARAT
On Fri, Jun 3, 2022 at 9:01 PM Lalit Suthar
wrote:
> Hi Sencer,
Based on my experience, this is the easiest one to start with:
https://django-auditlog.readthedocs.io/
On Mon, 6 Jun 2022 at 12:58, Mukul Verma wrote:
> i also have the question regarding this, is that i have to create auditing
> log file for all the activities performing in the project
i also have the question regarding this, is that i have to create auditing
log file for all the activities performing in the project smallest or
biggest may you please tell how to initiate this task from beginning.
*Thanks*
*Mukul Verma*
On Friday, 3 June 2022 at 23:32:04 UTC+5:30
Hi Sencer, signals will be helpful only if you are auditing on certain
models
but if you are trying to audit a set of views then middleware will be a
better choice since that will be more manageable
On Fri, 3 Jun 2022 at 18:29, Jason wrote:
> one good source when you have a question "is there
one good source when you have a question "is there anything in django that
does X?" is to go to djangopackages.org.
https://djangopackages.org/grids/g/model-audit/, for example, is a list of
packages for model auditing and history
On Friday, June 3, 2022 at 6:33:37 AM UTC-4 sencer...@gmail.com
Hi,
I've been planning to add audit logging to the project.
But, I can not decide which approach is the best;
Using signals or creating middleware?
Project needs to being log events on change of model object with these
informations below:
- If a record is inserted, updated and deleted:
-
7 matches
Mail list logo
