You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're seeing an issue where long log lines (above 8k characters or so) get wrapped. Unfortunately, the wrapped portion of the line isn't sent to papertrail with the hostname setting. So, for a particular server with a hostname set in log_files.yml, the first 8k characters of the log line will be sent to the names system, while the remaining characters will be sent to a system names after the IP of the server (or whatever the default hostname is).
The text was updated successfully, but these errors were encountered:
@jasonhutchens Are you still seeing this, and if so, is it with the --tls argument (which uses TCP) or without (UDP)? I'm guessing TCP+TLS given that 8k messages are getting through, but also wondering whether you saw any change about the behavior since creating this issue. Papertrail's own message length limits are documented here.
no, just had a look and haven't seen this for a while. however, that may be because we've changed what we're logging, and so aren't seeing really long lines anymore
We're seeing an issue where long log lines (above 8k characters or so) get wrapped. Unfortunately, the wrapped portion of the line isn't sent to papertrail with the hostname setting. So, for a particular server with a hostname set in log_files.yml, the first 8k characters of the log line will be sent to the names system, while the remaining characters will be sent to a system names after the IP of the server (or whatever the default hostname is).
The text was updated successfully, but these errors were encountered: