Using the logs sounds like an interesting possibility. They would be amazingly scalable (if one thinks about the fact that every single request on App Engine is saving a record). I may have to look at that as memcache (even dedicated) seems to occasionally hit a long enough snag to loose a considerable number of records in a row.
I wonder how fast one can read from the logs API and how quickly log events appear after the handler finishes a request. Will look at this. Big Query sounds more like a solution to analyse the data rather than storing it, but Mache does give me some ideas even if it's Java. I've seen an python look-alike called log2bq <http://code.google.com/p/log2bq/>(written by some Googlers). On Wednesday, 11 September 2013 23:35:41 UTC+10, barryhunter wrote: > > A possibly off the wall idea. Have a NOOP handler. Literally it does > nothing aside from return the correct HTTP Status code. > > Then extract the data from the standard App Engine Logs! Google have > obviouslly built a scalable logging infrastructure. Use it. The logs > include the GET paramaters and more. > > They can be downloaded in bulk > > https://developers.google.com/appengine/docs/python/tools/uploadinganapp#Python_Downloading_logs > > > > There is also a API for accessing logs from an app directly > https://developers.google.com/appengine/docs/python/logs/functions > but there have been some questions as to it scalablity/performance. > > > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
