Reading some previous discussions and things alluded to therein, some questions cropped up.
I'm considering an application that quite fundamentally requires access to all its request logs. So I guess I'd be recommended to use appcfg.py to periodically pull down the logs and append them to a txt file, or do whatever else I need to do to persist them. In previous discussion I saw Google folks say that logs are stored in a circular buffer. Meaning if you had enough requests, they'd overwrite older requests. Meaning that if you had enough requests or were downloading the logs sufficiently infrequently, you might lose logs. So question number 1: how big is the circular buffer for each application? 2: Changes to that buffer size could detrimentally impact on my application if revised downward (silently in particular), so are there any guarantees that this buffer size won't be reduced in the future? 3: Is there any possibility that this buffer could be exposed via the quota system so that an app could purchase a larger buffer size if it were helpful? I'm flashing forward to a busy site and somewhat worrying about how frequently I'll have to download the logs, and whether it would be feasible to download them with a certain frequency anyway (e.g. if the log download time is quite long - as I've found it can be). Any answers or advice would be very welcome. Thanks! -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
