-
Notifications
You must be signed in to change notification settings - Fork 285
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
Logs in docker #2818
Comments
Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on. If no reviewer appears after a week, a reminder will be sent out. |
Our goal is user experience to be as close as possible to a native core node. Having that said, logs being accessible locally is necessary and far from useless. As for pm2 logs you can always monitor it from outside the container. Whereas logs on stdout would fill up your filesystem with useless logs as the log you see on stdout gets actually recorded in a JSON format log per each container ID, separately it isn't end-user friendly at all. So we would prefer more controlled behaviour because of that. |
This issue has been closed. If you wish to re-open it please provide additional information. |
@faustbrian here you suggest that logs are abiut to In such infra the containers are managed by orchestration tools (kubernetes, openshift, swarm, compose). The logs from containers are digested into ELK cluster where they are parsed, labeled and enriched with additional info (hence - JSON, which makes it much easier). The logs on the filesytem on the nodes are rotated. Current scheme is absolutely not production ready and suitable only for sandbox envs. I suppose I have just to fork this repo to make it work, sorry for troubles. |
The dockerfile without pm2 solved that for me: #2820 |
When using docker (with orchestration tools or without) we prefer to have logs on stdout. This way we can get those logs and work with them (parse, alert, search etc).
Current config has logfile
~/.local/state/ark-core/mainnet/ark-relay-current.log
which basically repeats in cycle[2019-07-16 14:14:53.306] DEBUG: ark-relay 2.5.7
filling the container's filesystem with useless logsThe valuable logs are in
pm2 logs
, so we need tem to sent to stdoutThe text was updated successfully, but these errors were encountered: