Awesome (
https://github.com/unbit/uwsgi/commit/6056b5165353e4c4bb87e7913b5c9ac4656a64c1)
Thanks Roberto :)
On 13/09/13 05:25, Roberto De Ioris wrote:
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
Hansel & the PythonAnywhere team...
--
Hansel Dunlop
Developer
[email protected] @hanseldunlop
PythonAnywhere - a fully browser-based Python development and hosting
environment
<http://www.pythonanywhere.com/>
PythonAnywhere LLP
17a Clerkenwell Road, London EC1M 5RD, UK
VAT No.: GB 893 5643 79
Registered in England and Wales as company number OC378414.
Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
