-
Notifications
You must be signed in to change notification settings - Fork 162
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
Cleaner Scalyr logging support in latest scalyr-agent release #620
Comments
Thanks for your suggestion we will check the new version. @mohabusama, @apfeiffer85, @fmueller can you have a look? |
In case losing data is a cause for concern, according to one of the support reps in an email to me:
Anyways, there's no need to add that |
What do you mean by this? Just that we would lose the surrounding json structure? This would not be a problem IMO as it just makes it simpler to create custom parses when you don't have to worry about parsing json first. Thanks for letting us know about this! |
I just meant that the description from the release notes didn't indicate that you would still collect all the fields from the json log like "stream" |
Thanks @cyburgee Already created an issue here: zalando-incubator/kubernetes-log-watcher#49 |
Closing, because this repository does not own this component. Please check the referenced issue zalando-incubator/kubernetes-log-watcher#49 |
The latest release of the scalyr agent (https://github.com/scalyr/scalyr-agent-2/tree/v2.0.29) has better support for the json logs that come out of docker.
In their words:
It would be awesome if the images used by the logging-agent were updated to use that version. Also it would be nice if I could access the source for
registry.opensource.zalan.do/eagleeye/scalyr-agent
so I could help out myself.The text was updated successfully, but these errors were encountered: