no support for utf8 about log-shuttle HOT 3 CLOSED

This is a pretty major bug, since most/all Rails webapps employ a UTF8 form parameter when submitting POST requests to apps. This effectively removes all app logging from heroku. All log entries after an UTF-8 POST request are gone.

from log-shuttle.

I kept this in mind while looking at another issue today and log-shuttle keeps the incoming message as a []byte. The only time it manipulates it if it's len(message) > 10000. Frames are length prefixed in the body as well. So as long as utf8 messages are < 10000 bytes in length we should be fine atm.

Maybe heroku/logplex is to blame, although I think it treats messages similiarly.

We'll have to put together an end-to-end utf8 test probably.

I'm leaving this open for now until I can have a chance to write a test that exercises things.

from log-shuttle.

Turns our the core problem was this: phusion/passenger@48f9486

I've tested that log-shuttle relays utf8 fine (as long as the log line is under 10000 bytes as there is likely a problem with splitting in the middle of a utf8 "character".

from log-shuttle.