Ok, figured it out and it was obvious: Python logging was not being
explicitly told to log to stdout. Here's the logging config that I
used:
logging.basicConfig(
stream=sys.stdout,
level=logging.DEBUG,
format='"%(asctime)s %(levelname)8s %(name)s - %(message)s"',
datefmt='%H:%M:%S'
)
On Jun 10, 2:02 am, jasonpriem <[email protected]> wrote:
> Hi,
> My Python Heroku installation works locally in Foreman, but breaks on
> Heroku. No worries, thinks I, I'll just "Heroku logs -t" and I'm
> golden.
>
> I'm not golden.
>
> The only output I'm seeing is messages from Heroku itself; none of my
> DEBUG and INFO log entries are showing up at all. It's going to be
> impossible to fix this unless I can see that information, so I'd love
> any help y'all can give. I found that a similar post [1], but it was
> in Ruby and the solution was to send logs to stdout. I'm already doing
> that, and can see 'em just fine when I run locally in Foreman.
>
> -jason
>
> [1]http://groups.google.com/group/heroku/browse_thread/thread/2d62f0633e...
--
You received this message because you are subscribed to the Google
Groups "Heroku" group.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en
