> Hello list
>
> We are currently trying to get uWSGI vassals to log to a rsyslog server.
> The good news is that it's working! UDP packets are arriving. However
> they are not being marked with the syslog "facility" that we think we
> are applying in the vassal config.
>
>      logging = rsyslog:<rsyslog-server-ip>:<port>,local1
>
> They do show up in syslog with a "local1" somewhere in the formatted log
> entry. But we can't capture them via this facility. We Can capture them
> with the "daemon", and "mark" facilities so they are tagged in some way.
>
> Has anyone else got this working?
>
> Cheers
>
>

The syslog protocol is pretty funny, this is the format:

<XX> Fri Sep 13 06:21:17 2013 hostname application: msg

XX is the so-called "priority" and it is described here:

http://www.ietf.org/rfc/rfc3164.txt

on section 4.1.1

The value (til now) is hardcoded to '29'

((system daemons (3)) * 8) + (Notice: normal but significant condition (5))

The current syntax is:

rsyslog:<rsyslog-server-ip>:<port>,hostname

the new one (available in 1.9.16 or with this patch:
https://github.com/unbit/uwsgi/commit/6056b5165353e4c4bb87e7913b5c9ac4656a64c1)
is

rsyslog:<rsyslog-server-ip>:<port>,hostname,priority

so you have to do some math for the right priority value and then you are
ready

-- 
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to