-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scalyr: Use parse_lines_as_json for docker containers #49
Comments
Hi @mohabusama, I would also like to tackle this issue. |
Hi @eicnix ,, yep sure, please go ahead 😄 My only remark would be to make it configurable ( I haven't really looked on how this works, but my main concern would be to make sure we do not break existing manifests which set a specific parser expecting the normal JSON message. If Scalyr agent will just add extra attributes and do not modify the message (which parsers depend on), then migration would be easier. |
With the new configuration parameter `WATCHER_SCALYR_PARSE_LINES_JSON` the Scalyr agent can be configured to parse log lines as JSON entries which is useful to process raw Docker logs. This behaviour is disabled by default.
With the new configuration parameter `WATCHER_SCALYR_PARSE_LINES_JSON` the Scalyr agent can be configured to parse log lines as JSON entries which is useful to process raw Docker logs. This behaviour is disabled by default.
@eicnix I didn't have much time to properly test this change. Could you try with this image: registry.opensource.zalan.do/eagleeye/kubernetes-log-watcher:0.20-2-g5e1e18f |
As described here: https://github.com/scalyr/scalyr-agent-2/releases/tag/v2.0.29
Also suggested here: zalando-incubator/kubernetes-on-aws#620
The text was updated successfully, but these errors were encountered: