-
-
Notifications
You must be signed in to change notification settings - Fork 88
Improving request logging. #90
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
Comments
The simplest way to get more information is to run with That being said, it produces a lot of information. We should probably provide a middle ground for just logging requests. Logging like this impacts performance, so it's not by default. A simple solution which works everywhere is to use a logging middleware. I'll think about the best way to solve this issue. |
i will try it. thanks. If there is something that I can do to help, just let me know. |
I found that the problem with the squelched logs in Falcon lies with foreman. Switching over to hivemind (another Procfile-based process manager) fixed it. |
Do you know why it made a difference? |
Not really. But in the hivemind readme (https://github.com/DarthSim/hivemind) they write |
And |
Yes that makes sense, if you want to capture TTY output then you need to simulate a TTY for the child process. And you are correct this is not Falcon specific. |
yeah just wanted to note my findings here to help close this issue, unless you don't like closing issues 🤔😅 |
I'm trying to use falcon on production in one app that I'm creating. Now I'm blind of logs, I don't know what happen when I run the app it don't show any logs of requests only the database interactions.
I'm running my app using
foreman
with the commandfalcon serve -b http://0.0.0.0:9292
. Everything is running on a container. I didn't change anything on theconfig/enviroment/production.rb
it's running all the rails default.Can someone help me with this?
The text was updated successfully, but these errors were encountered: