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
And a snippet like this to the fluent config should do the trick (totally untested):
<source>
@type tcp
@id in_application_tcp
tag "lagoon.#{ENV['CLUSTER_NAME']}.application"
port 5140
<parse>
@type json
</parse>
</source>
And then we need to document how to get logs there in the right format. And note that if you don't escape newlines (so a line has half a JSON object), the log message will be dropped.
lagoon-logging currently supports UDP for application logs.
In order to support more logging transports more easily (such as Winston, Pino etc), we should also accept TCP logs on a separate port
The text was updated successfully, but these errors were encountered: