We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be interesting to set some guidelines for a production deployment. For example:
When using a virtual machine, the simplest way is to create a systemd service to run the logger and output the logs to the folder /var/log/.
/var/log/
It's also important to add a logrotate rule to automatically compress and delete old log files.
To be defined.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It would be interesting to set some guidelines for a production deployment. For example:
Using a virtual machine (e. g. AWS ec2, digital ocean's droplet)
When using a virtual machine, the simplest way is to create a systemd service to run the logger and output the logs to the folder
/var/log/
.It's also important to add a logrotate rule to automatically compress and delete old log files.
Using docker
To be defined.
Integration with ELK stack
To be defined.
The text was updated successfully, but these errors were encountered: