Two things which I've encountered that might be solved by better logging: 1. I'd like the option to see the actual SQL queries (just temporarily). Sure you can pull in the production database and test locally but it's slow and awkward. Particularly as the DB size grows, it becomes impractical 2. 404 errors fall outside the Hoptoad/Exceptional responsibility and that's something that I'd like to check for occasionally. Something like an errors.log file.
One other thing: some people seem to want to archive their log files (for whatever purpose - I'm not one of them) and perhaps dumping them out to an S3 account daily would satisfy their needs (possibly for an additional charge) Having said all that, I think I've adapted to the "Heroku way" and can fix most problems from the Hoptoad report. Jamie On Feb 25, 3:59 am, Oren Teich <[email protected]> wrote: > One of the top requests we've had is for "better logging". I'm looking for > specific feedback on the problems you've run into, and who "better logging" > would help you solve your problems. While there are of course obvious > cases, I want to make sure we get some real use cases straight from you > guys . Either here or off-list, I'd like to start a discussion on the > problems you've run into with Heroku logs, limitations of solutions like > exceptional or hoptoad, and what you'd like to see from Heroku when you > think of "logs". > > Thanks, > Oren -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. 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.
