The logs, while good to have, are a super PITA to use. Things that would be great to fix:
- The search option labelled 'Since' is exactly the opposite of what it says. Everyone i've ever spoken to gets confused by this, the logs work backwards from this time, not forwards. I must have helped at least 10 people understand this to use the logs. - On the dashboard you can see errors in the last 24 hours, and if you click through they take you into the logs to see what the problem is. I have never, ever seen this work. The filter it applies (status and path) flat out doesn't work and apparently never has. - It would be super, super useful if you could filter out different log levels. For example, if you filter for anything with info and above, you still see all debug logs. This means even when looking for errors or warnings, you have to look by eye through plenty of lines of logs. An extra option to show only log levels above a certain level would be really useful - The ability to control how long to search backwards through logs would be great. Sometimes, you really need to know if something happened at all in the last month, and i'd rather pay to search a months or a years worth of logs than sit there clicking 'Use Next link to search older records.'. Maybe having the timestamp filter as a 'from' and 'to', rather than 'Since' would help. I appreciate that distributed logging and live log search is a non-trivial problem, but it feels like someone already has done all the hard work and that the log viewer just sort of stopped progressing at some point. Having said that, the addition of being able to search again for older entries back through time was really useful. Before that you had to be lucky enough to catch problems pretty quickly. On Saturday, May 25, 2013 7:32:16 AM UTC+10, Takashi Matsuo (Google) wrote: > > > Thanks Matthew, > > I confirmed that you can download logs with instance_id by running the > Python appcfg.py with the '--include_all' option as follows: > $ appcfg.py request_logs --oauth2 -A APP_ID --version VERSION > --include_all LOG_FILENAME > > Unfortunately, it doesn't seem Java appcfg have that option yet though. > > > On Fri, May 24, 2013 at 2:00 PM, Matthew Blain > <[email protected]<javascript:> > > wrote: > >> The instance is available today in the logs you can download. I recently >> updated logparser.py to not fail when it shows up in the logs. >> >> https://code.google.com/p/google-app-engine-samples/source/browse/trunk/logparser/logparser.py >> >> (Looks like I didn't update the docstring for this, but the fundamentals >> are correct.) >> >> >> On Friday, May 24, 2013 12:24:24 PM UTC-7, Takashi Matsuo (Google) wrote: >> >>> >>> As Vinny said, certainly BigQuery is something you can consider. >>> Here is another project for ingesting App Engine logs into BigQuery: >>> https://code.google.com/p/**log2bq <https://code.google.com/p/log2bq> >>> >>> -- Takashi >>> >>> >>> On Fri, May 24, 2013 at 11:49 AM, Vinny P <[email protected]> wrote: >>> >>>> Hello Kristopher, >>>> >>>> >>>> On Friday, May 24, 2013 10:51:23 AM UTC-5, Kristopher Giesing wrote: >>>>> >>>>> I'm getting enormously frustrated by this. Am I missing something >>>>> about the admin console, or is its search function really this broken? >>>>> Is >>>>> there some way to get more verbose logging from the logs-download feature >>>>> of appcfg.sh? >>>>> >>>> >>>> Yup, you're correct. Searching logs can be a PITA. >>>> >>>> Personally, I use a combination of a homebuilt logging inspector (a >>>> backend using the Logging API to inspect error logs) and Google BigQuery >>>> to >>>> analyze my logs. Streak wrote up a blog entry about using Google BQ to >>>> inspect logging, you can read it here: http://blog.streak.com/** >>>> 2012/07/export-your-google-**app-engine-logs-to.html<http://blog.streak.com/2012/07/export-your-google-app-engine-logs-to.html> >>>> . >>>> >>>> >>>> >>>> ----------------- >>>> -Vinny P >>>> Technology & Media Advisor >>>> Chicago, IL >>>> >>>> My Go side project: http://invalidmail.com/ >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Google App Engine" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to google-appengi...@**googlegroups.com. >>>> To post to this group, send email to google-a...@googlegroups.**com. >>>> >>>> Visit this group at http://groups.google.com/** >>>> group/google-appengine?hl=en<http://groups.google.com/group/google-appengine?hl=en> >>>> . >>>> For more options, visit >>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>> . >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Takashi Matsuo | Developers Programs Engineer | [email protected] >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to >> [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/google-appengine?hl=en >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > Takashi Matsuo | Developers Programs Engineer | [email protected]<javascript:> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
