Anyone with any idea how to solve this problem?
Thanks in advance.
--
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+unsubscr...@googlegroups.com.
We want to separate out activity per client. This can be useful in many
ways. Ex. 1) easier debugging of issues. 2) Running some analytics per
client by looking at his log file. 3) Clients which are no longer a
customer, their logs can be safely moved to lower storage tiers. etc.
Basically to
Well sites framework makes possible to do for example multitenancy
inside database.
But apparently that is not your case. So why you like to log something
per user? What's the real usecase here?
On 25.11.2015 11:45, Nikunj Badjatya wrote:
Thank you for your response.
Well our application is
Thank you for your response.
Well our application is single site only. AFAIK, sites framework is useful
when your django application serves multiple sites.
Can you throw some more light on what can be achieved using sites ?
I would like to evaluate all available options.
Thanks.
On Tuesday,
Hi,
Problem is that you quite certainly have different users and several
processess/threads which would lead logging configuration per request.
Is there a reason you don't use something like sites framework to
differentiate clients?
On 24.11.2015 12:22, Nikunj Badjatya wrote:
Hello,
Hello,
Currently for our application, all django logs are generated and kept at
'/var/log/django.log'
We want to have different log files for different clients. i.e.
/var/log/client-1/django.log
/var/log/client-2/django.log
/var/log/client-3/django.log
The request object has
6 matches
Mail list logo
