Re: ORM for structured Logs

Hi Marten,

Am Donnerstag, 6. April 2017 14:10:58 UTC+2 schrieb knbk:

Hi Thomas,

The primary purpose of logging is to catch and examine errors. If something went wrong, you want to know when and why. Logging to a database increases the complexity and greatly increases the number of things that can go wrong. The last thing you want to find out when retracing an error is that you don't have any logs because the logging system failed. You may also need to log errors that happened during startup, before a database connection can be established. Logging to file is the simplest method, and has the least chance of failure. That's why you should always log to file. 

The two options are not mutually exclusive. Like you said, times have changed, and the overhead to store logs both in a file and in a database are nowadays acceptable. If you have a good reason to store the logs in a database, then go ahead. Just remember that it should be in addition to file-based logging. 

Yes, you are right. During the initialization of processes no db connections exists yet. I don't like redundancy but here its needed for a higher availability.

Thank you for your reply.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a9a0fe4e-4b65-4ceb-8336-cc4ceeb82f2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.