forked from ontoportal/ontologies_api
-
Notifications
You must be signed in to change notification settings - Fork 10
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
excessive logging in unicorn #66
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unicorn generates 3 logs:
production.log - access log
unicorn.stderr.log - access log + exeptions/error stack traces
unicorn.stdout.log - app notifications
This is not an ideal situation for the appliance. If stderr_path or stdout_path is not set in unicorn.rb then stderr log goes to syslog. Single API hit generates nearly identical entry in at least 3 log files (including nginx which fronts unicorn)
we should look into refactoring the way logging is done in the ontologies_api
The text was updated successfully, but these errors were encountered: