> Yeah, that sounds right. It looks like .16 may do what I need :) I will
> await that and try.
>
> Thank you!
Just as a note, in addition to "msgpack" encoder, a "json" one has been added
log-encoder = json {"msg":"${msg}", "foo":"bar"}
>
> -Jason
>
> On 9/6/13 12:28 PM, "Roberto De Ioris" <[email protected]> wrote:
>
>>
>>> Howdy,
>>>
>>>
>>>
>>> Hmm, so it sounds like the only real way is to have uWSGI do it; or
>>> beat
>>> on the log once on the hard drive. Having a logstash format on uWSGI
>>> would be awesome. :)
>>>
>>> Thanks!
>>> -Jason
>>
>>
>>AFAIK there is no "logstash" format. It expects some kind of key-value
>>object, so the upcoming log-encoder should be more than enough.
>>
>>As the only encoder i plan to release in 1.9.16 is the msgpack and
>>logstash supports it i suppose you only need to choose the transport
>> (udp,
>>tcp, zeromq, rsyslog...)
>>
>>am i right ?
>>
>>
>>--
>>Roberto De Ioris
>>http://unbit.it
>>_______________________________________________
>>uWSGI mailing list
>>[email protected]
>>http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
--
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
