Re: Better logging feedback
Oren, I am glad that you bring up this issue. As you know, I have been working on the problem of logging and analytics for Heroku apps for a while now, and have recently finished building a modular architecture to support the capture, analysis, and acting on logging data --beyond the passive reporting of low-level events, to encompass user-defined, application-level events and actions. In short, our solution provides 'logging and analytics' as a service. Through a simple gem and our hosted service, you can: * automatically record web request information and have it sent (over a secure channel) to our servers, * programmatically log any kind of semi-structured data (arbitrary schema-less key/value pairs), anywhere in your application, and * have full access to your data through a RESTful API and a powerful query language On top of this basic architecture we have built powerful tools to analyze and report on the recorded data --addressing the issues raised in this thread by Jamie and Arun, and supporting many other use cases as well. For example, we have: * a tool to 'tail -f' whatever your applications are recording while filtering out unwanted records (e.g. list only 404s) * a tool that lets you group your data by different criteria and compute totals over the groups (e.g., count of searches performed, by search term) * an application to create a private RSS feed with the log entries that match arbitrary criteria (e.g, new accounts as they are created, along with relevant information about them) * dashboards and charts to get a quick picture of what's going on in your applications (e.g., number of requests by unit of time, or number of accounts by gender, etc.) Thanks to the RESTful API and the powerful query language, the architecture is highly extensible and makes it easy to write scripts that actively monitor the data and react to it. We have also written, for example, * a tiny Rack middleware that records HTTP_X_HEROKU_QUEUE_DEPTH, and a separate monitoring application that runs regular queries against the database. If in a given interval it finds that the log values exceed a user-defined value, the script makes calls to the Heroku API to start new dynos --providing automatic up-scaling for your apps. * a monitoring tool that sends you email whenever the number of failed logging attempts per unit of time exceeds a certain threshold. We are ready to begin a private beta, and are looking for volunteers. If you're interested, please send me an email to schap...@pomelollc.com. I'll be delighted to give out free accounts and see what people think of it and, more importantly, what solutions and ideas you build with our solution. Thanks, - Agustin -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Better logging feedback
Oren, I am glad that you bring up this issue. As you know, I have been working on the problem of logging and analytics for Heroku apps for a while now, and have recently finished building a modular architecture to support the capture, analysis, and acting on logging data --beyond the passive reporting of low-level events, to encompass user-defined, application-level events and actions. In short, our solution provides 'logging and analytics' as a service. Through a simple gem and our hosted service, you can: * automatically record web request information and have it sent (over a secure channel) to our servers, * programmatically log any kind of semi-structured data (arbitrary schema-less key/value pairs), anywhere in your application, and * have full access to your data through a RESTful API and a powerful query language On top of this basic architecture we have built powerful tools to analyze and report on the recorded data --addressing the issues raised in this thread by Jamie and Arun, and supporting many other use cases as well. For example, we have: * a tool to 'tail -f' whatever your applications are recording while filtering out unwanted records (e.g. list only 404s) * a tool that lets you group your data by different criteria and compute totals over the groups (e.g., count of searches performed, by search term) * an application to create a private RSS feed with the log entries that match arbitrary criteria (e.g, new accounts as they are created, along with relevant information about them) * dashboards and charts to get a quick picture of what's going on in your applications (e.g., number of requests by unit of time, or number of accounts by gender, etc.) Thanks to the RESTful API and the powerful query language, the architecture is highly extensible and makes it easy to write scripts that actively monitor the data and react to it. We have also written, for example, * a tiny Rack middleware that records HTTP_X_HEROKU_QUEUE_DEPTH, and a separate monitoring application that runs regular queries against the database. If in a given interval it finds that the log values exceed a user-defined value, the script makes calls to the Heroku API to start new dynos --providing automatic up-scaling for your apps. * a monitoring tool that sends you email whenever the number of failed logging attempts per unit of time exceeds a certain threshold. We are ready to begin a private beta, and are looking for volunteers. If you're interested, please send me an email to schap...@pomelollc.com. I'll be delighted to give out free accounts and see what people think of it and, more importantly, what solutions and ideas you build with our solution. Thanks, - Agustin -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Better logging feedback
>From a relative beginner's perspective, it would be nice for the 500 page to display something useful on the first time (or first few times) a new application is loaded. Overwriting the application's ability to have a custom 500 page is probably a bad idea but giving some minimal direction would help me. If the app is broken, I want as much information as possible on how to get it going. Ideas: -links to the documentation -please run "heroku logs" -advice for add-ons Sunny On Thu, Feb 25, 2010 at 9:25 PM, Oren Teich wrote: > Nothing else from anyone? This comes up all the time - is exceptional > sufficient? > > Oren > > > On Thu, Feb 25, 2010 at 8:21 AM, Oren Teich wrote: > >> Rails doesn't show SQL queries when running in production mode. New Relic >> is your best bet for seeing this stuff, regardless of platform. >> >> 404 is an interesting one. Thanks! >> >> Other issues with logging today? >> >> Bueller? >> >> Oren >> >> On Thu, Feb 25, 2010 at 3:59 AM, Jamie Lawrence wrote: >> >>> 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 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 her...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> heroku+unsubscr...@googlegroups.com >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/heroku?hl=en. >>> >>> >> > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Better logging feedback
Didn't work. I also tried restarting the dyno and same error. On Feb 25, 2010, at 22:25 , David Dollar wrote: > Give it a try now, we just pushed out some fixes to the Exceptional > integration. > > On Thu, Feb 25, 2010 at 10:05 PM, Gustavo Beathyate > wrote: >> I haven't been able to install exceptional for over a week. I keep getting >> internal server error messages… >> >> >> >> On Feb 25, 2010, at 21:25 , Oren Teich wrote: >> >>> Nothing else from anyone? This comes up all the time - is exceptional >>> sufficient? >>> >>> Oren >>> >>> On Thu, Feb 25, 2010 at 8:21 AM, Oren Teich wrote: >>> Rails doesn't show SQL queries when running in production mode. New Relic >>> is your best bet for seeing this stuff, regardless of platform. >>> >>> 404 is an interesting one. Thanks! >>> >>> Other issues with logging today? >>> >>> Bueller? >>> >>> Oren >>> >>> On Thu, Feb 25, 2010 at 3:59 AM, Jamie Lawrence wrote: >>> 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 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 her...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> heroku+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/heroku?hl=en. >>> >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Heroku" group. >>> To post to this group, send email to her...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> heroku+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/heroku?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Heroku" group. >> To post to this group, send email to her...@googlegroups.com. >> To unsubscribe from this group, send email to >> heroku+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Better logging feedback
Give it a try now, we just pushed out some fixes to the Exceptional integration. On Thu, Feb 25, 2010 at 10:05 PM, Gustavo Beathyate wrote: > I haven't been able to install exceptional for over a week. I keep getting > internal server error messages… > > > > On Feb 25, 2010, at 21:25 , Oren Teich wrote: > >> Nothing else from anyone? This comes up all the time - is exceptional >> sufficient? >> >> Oren >> >> On Thu, Feb 25, 2010 at 8:21 AM, Oren Teich wrote: >> Rails doesn't show SQL queries when running in production mode. New Relic >> is your best bet for seeing this stuff, regardless of platform. >> >> 404 is an interesting one. Thanks! >> >> Other issues with logging today? >> >> Bueller? >> >> Oren >> >> On Thu, Feb 25, 2010 at 3:59 AM, Jamie Lawrence wrote: >> 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 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 her...@googlegroups.com. >> To unsubscribe from this group, send email to >> heroku+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en. >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Heroku" group. >> To post to this group, send email to her...@googlegroups.com. >> To unsubscribe from this group, send email to >> heroku+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Better logging feedback
I haven't been able to install exceptional for over a week. I keep getting internal server error messages… On Feb 25, 2010, at 21:25 , Oren Teich wrote: > Nothing else from anyone? This comes up all the time - is exceptional > sufficient? > > Oren > > On Thu, Feb 25, 2010 at 8:21 AM, Oren Teich wrote: > Rails doesn't show SQL queries when running in production mode. New Relic is > your best bet for seeing this stuff, regardless of platform. > > 404 is an interesting one. Thanks! > > Other issues with logging today? > > Bueller? > > Oren > > On Thu, Feb 25, 2010 at 3:59 AM, Jamie Lawrence wrote: > 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 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 her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > > > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Better logging feedback
Nothing else from anyone? This comes up all the time - is exceptional sufficient? Oren On Thu, Feb 25, 2010 at 8:21 AM, Oren Teich wrote: > Rails doesn't show SQL queries when running in production mode. New Relic > is your best bet for seeing this stuff, regardless of platform. > > 404 is an interesting one. Thanks! > > Other issues with logging today? > > Bueller? > > Oren > > On Thu, Feb 25, 2010 at 3:59 AM, Jamie Lawrence wrote: > >> 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 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 her...@googlegroups.com. >> To unsubscribe from this group, send email to >> heroku+unsubscr...@googlegroups.com >> . >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en. >> >> > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Better logging feedback
Rails doesn't show SQL queries when running in production mode. New Relic is your best bet for seeing this stuff, regardless of platform. 404 is an interesting one. Thanks! Other issues with logging today? Bueller? Oren On Thu, Feb 25, 2010 at 3:59 AM, Jamie Lawrence wrote: > 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 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 her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Better logging feedback
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 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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Better logging feedback
Great place to start. The production.log rails puts out is pretty gnarly to quickly scan - it has a lot of lines for each request, plus lots of spurious info. What specifically are you looking at in the log to see this kind of stuff? Is it access log type stuff? something specific to what is in the production.log file? Oren On Wed, Feb 24, 2010 at 8:56 PM, Arun Thampi wrote: > One thing I miss from having my own VPS is the ability for me to tail a > particular log (to quickly scan for unauthorized bots/spiders hitting an > app, etc.): a command like `heroku tail production.log` would be very sweet. > > Cheers, > Arun > > On Thu, Feb 25, 2010 at 11:59 AM, Oren Teich 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 her...@googlegroups.com. >> To unsubscribe from this group, send email to >> heroku+unsubscr...@googlegroups.com >> . >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en. >> > > > > -- > It's better to be a pirate than join the Navy - Steve Jobs > http://mclov.in > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Better logging feedback
One thing I miss from having my own VPS is the ability for me to tail a particular log (to quickly scan for unauthorized bots/spiders hitting an app, etc.): a command like `heroku tail production.log` would be very sweet. Cheers, Arun On Thu, Feb 25, 2010 at 11:59 AM, Oren Teich 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 her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- It's better to be a pirate than join the Navy - Steve Jobs http://mclov.in -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Better logging feedback
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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
