8000 logging · Issue #62 · stain/jena-docker · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

logging #62

8000 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.

Sign up for GitHub

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

Jump to bottom
Open
plasticfist opened this issue Dec 27, 2021 · 2 comments
Open

logging #62

plasticfist opened this issue Dec 27, 2021 · 2 comments

Comments

@plasticfist
Copy link
plasticfist commented Dec 27, 2021 •
edited
Loading

nice docker, streaming works well for the very large triple store riot conversions I'm running however it appears the default logging creates a massive -json.log file in /var/lib/docker/container/xxx logging in json format every triple processed. For now I'm force pruning after every run, but that isn't ideal, simply suppressing the (unused?) logging inside the container would be much better.

I do need to capture stdout and stderr msgs outside the container, but I hope to suppress creation of that -json.log file inside the container.

What is the best way?
@infinite-dao
Copy link

You can design your docker container how restrict the log files, e.g. together with docker run … I did it like:

docker run --name "name-of-your-container-to-be-created" …otheroptions… \
  --log-opt max-size=300m \
  --log-opt max-file=3 \
  --log-opt compress=true \
…

I guess the official documentation is on https://docs.docker.com/config/containers/logging/local/ and those sections there …

@joelduerksen
Copy link
joelduerksen commented Feb 8, 2023 •
edited
Loading

Thank you for this! Good stop gap measure, and generally useful across all docker images, agree.
OP question however was, is there any way to control the verbosity logging of this application. It is sending a massive deluge of informational debugging text into the log. Most users would only want to only see error/critical messages in the log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@infinite-dao @plasticfist @joelduerksen
0