[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uwsgi
Subject:    [uWSGI] logstash best practice
From:       roberto () unbit ! it (Roberto De Ioris)
Date:       2014-03-26 11:11:51
Message-ID: ab9b3bf380ec0d60d6641c2085ea0cdc.squirrel () manage ! unbit ! it
[Download RAW message or body]


>>> The claim on http://uwsgi-docs.readthedocs.org/en/latest/Logging.html
>>> that
>>>  ... logger = file:/tmp/foobar # This logger will log everything as
>>> it's not named ...
>>>
>>> seems to not be true, it doesn't log to tty like that
>>>
>>
>> can't reproduce the problem:
>>
>> ./uwsgi --logger file:/dev/tty -s :3031 -M
>>
>> works
>>
>> ./uwsgi --logger file:/dev/tty -s :3031 -M --logger file:/dev/tty
>>
>> works with doubled lines
>
> uwsgi --logger file:/dev/tty -s :3031 -M --logger "stdout
> file:/dev/tty" --log-route "stdout ^"
>
> this shows just a single line .. and adding --log-encoder
> "prefix:stdout !!!" shows it's the stdout logger that displays the
> output.
> _______________________________________________
> uWSGI mailing list
> uWSGI at lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>

Oh ok, it is the log routing that has precedence over unnamed routes.

If at least one rule matches the unnamed loggers are not called

https://github.com/unbit/uwsgi/blob/master/core/logging.c#L1405

i have changed the doc from "everything" to "everything else"

-- 
Roberto De Ioris
http://unbit.it

[prev in list] [next in list] [prev in thread] [next in thread]