It may not be exactly what you're looking for but you way want to take a look at our LogDigger tool and service (http://logdigger.com/)
With LogDigger you can capture logged application errors with additional request details (URL, request params, etc.). For GAE apps you can collect API and CPU time, etc. You can find GAE specific notes here: http://logdigger.com/logdigger-connector/java-logging-app-engine By default it will capture only requests when an exception is logged but there's a way (still undocumented) to force capture in other scenarios too. (We're still looking into providing additional logging options so any feedback and feature requests are appreciated.) For the curious, My LogDigger service is running on GAE (HR). Radomir On Apr 1, 2:54 am, Jeff Schnitzer <j...@infohazard.org> wrote: > On Thu, Mar 31, 2011 at 5:10 PM, Kyle Baley <k...@baley.org> wrote: > > We want to be somewhat proactive about warnings or higher in our logs so > > we're looking at a way of being notified if they occur. First thought was to > > use log4j and the email appender. This is fine but won't scale as more > > people use the app since we'll get inundated with emails. So we're looking > > at another option: parsing the logs and emailing every half hour if there > > are new warnings/errors/critical messages. Any suggestions on how to do > > this? > > Based on my research, it looks like we would need to set up a job to > > download the logs with appcfg.py at regular intervals and parse them outside > > of the app. Looking for other potential options. > > If you productize something like this, I would pay money for it. > > Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
