[Flask] User specific log files

[Kelvin M]

Hi Kevin,

What are you trying to accomplish with multiple log files?  In the past,
the approach that I/we've taken is to just use a log aggregator.  Either,
Splunk or ELK (ElasticSearch, LogStash, Kibana).

With both, you index all log messages and can then create reports or views
for users independently.

I know that ELK is really easy to set up and free.

Would something like that work for you?

Regards,
Kelvin

On Mon, Feb 1, 2016 at 5:26 PM, Robert Grant <robertlagrant at gmail.com>
wrote:

> Hi Kevin
>
> Just a couple of quick questions:
>
> 1) Do you have enough users to just log to a database and record a
> username with each log line? Just a suggestion to consider.
> 2) Can you post a minimal, verifiable and complete example of your first
> attempt to give people something solid to critique?
>
> Thanks
>
>
> Rob
>
> On Mon, Feb 1, 2016 at 8:55 PM, Kevin Stone <Kevin.Stone at jax.org> wrote:
>
>> ​Hi,
>>
>>
>> I am not the most familiar with the python logging framework, and I think
>> I need some help on developing an approach for creating user specific log
>> files in Flask. It would be even better if someone has already done this
>> before and could share their pattern.
>>
>>
>>
>> The problem I want to solve is this:
>>
>> 1) user1 and user2 both log in to the app
>>
>> 2) user1's activity is logged in "user1.log". user2's activity is logged
>> in "user2.log".
>>
>> 3) No other user's activity should appear in that user's log file.
>>
>>
>>
>> Ideally, I would like to tap into existing loggers that I have (e.g. the
>> app logger and the SQLAlchemy logger), but I don't know if that is
>> possible. My first naive attempt simply registers additional handlers at
>> login time to the app.logger. This created the appropriate log files, but
>> they had all activity from all users writing to them.
>>
>>
>>
>> Any help or advice would be appreciated.
>>
>> Thanks,
>>
>> -Kevin
>>
>> The information in this email, including attachments, may be confidential
>> and is intended solely for the addressee(s). If you believe you received
>> this email by mistake, please notify the sender by return email as soon as
>> possible.
>>
>> _______________________________________________
>> Flask mailing list
>> Flask at python.org
>> https://mail.python.org/mailman/listinfo/flask
>>
>>
>
> _______________________________________________
> Flask mailing list
> Flask at python.org
> https://mail.python.org/mailman/listinfo/flask
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/flask/attachments/20160202/6446285d/attachment.html>