Help me out here; I must be missing something really obvious.
I have a Padrino app running on Heroku. In boot.rb, in the block passed to Padrino.before_load
, I have the following lines:
Padrino::Logger::Config[:production][:log_level] = :info
Padrino::Logger::Config[:production][:stream] = :stdout
And in the before
block in app.rb, I have calls to logger.info
scattered throughout.
This logs to standard out just fine on my development machine. But when I check my Heroku logs:
heroku logs -t -s app
...I don't see anything (just the initial 3 lines of startup info from the Thin server).
What am I missing?
Some points of clarification in response to culix:
- Switching to
heroku logs -s app
after the app starts does not change anything for me. - I tried installing Papertrail. Which actually looks quite nice! But it still doesn't have the log messages I'm looking for.
- That is a good question! I really did just have calls to
logger.info
in thebefore
block. I will add more logging and check back, after I finish updating this question. - Now that you ask: my app doesn't seem to be logging anything either when I switch to running in "production" (after changing database.rb to just point to the development DB). I think this means I'm just fundamentally configuring Padrino logging incorrectly. Thanks for asking this question!
- Latest boot.rb is committed.
- Nope—not (intentionally) messing with stdout in any way.
Obviously the first thing I should spend time investigating is #4 above; that's what I will do now. Then, in case it yields nothing, on to #3.