On Wed, Sep 11, 2013 at 8:43 AM, Barry Hunter <[email protected]> wrote:
> Also maybe BigQuery could be used for the 'long term storage'? > > I use BigQuery myself, and I can second Barry's comment. It's easy to integrate with App Engine logs and analyze them. On Sun, Sep 8, 2013 at 10:20 PM, Ezequiel Muns <[email protected]> wrote: > I'd appreciate people's opinions/advice. > Depending on your use case, have a NOOP handler or a simple handler which exports the headers to JSON and prints it out into logging. Have a cron job routinely export logs into a Cloud Storage bucket, then use a Compute Engine machine/App Engine app to do any log cleanup required. Another option is to get a big instance (an F4_1G for example) and record the request logs into the instance's memory (not persistent storage). When the record gets too big, save it all at once into GCS, wipe the instance's in-memory records, rinse and repeat. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.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 [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.
