Ryan Petrello e52cebc28e rsyslogd: use %rawmsg-after-pri% instead of %msg% ... after some prolonged RFC reading and tinkering w/ rsyslogd... cpython's SysLogHandler doesn't emit RFC3164 formatted messages in the format you'd expect; it's missing the ISO date, hostname, etc... along with other header values; the handler implementation relies on you to specify a syslog-like formatter (we've replaced all of this with our own *custom* logstash-esque formatter that effectively outputs valid JSON - without dates and other syslog header values prepended) because of this unanticipated format, rsyslogd chokes when trying to parse the message's parts; AWX is emitting: <priority>RAWJSON ...so the usage of `%msg%` isn't going to work for us, because rsyslog tries to parse *all* of the possible headers (and yells, because it can't find a date to parse): see: https://www.rsyslog.com/files/temp/doc-indent/configuration/properties.html#message-properties this is fine, because we don't *need* any of that message parsing anyways; in the end, we're *just* interested in forwarding the raw JSON/text content to the third party log handler		2020-04-13 11:44:00 -04:00
..
check_vars/tasks	Merge pull request #5420 from Spredzy/yamllint	2019-12-04 13:42:56 +00:00
image_build	Add action to default rsyslog.conf so supervisor starts correctly the first time	2020-04-13 11:44:00 -04:00
image_push/tasks	yamllint: Make all files in awx pass yamllint	2019-12-02 15:12:51 +01:00
kubernetes	rsyslogd: use %rawmsg-after-pri% instead of %msg%	2020-04-13 11:44:00 -04:00
local_docker	Move supervisor and rsyslog sock files to their own dirs under /var/run	2020-04-13 11:43:59 -04:00