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-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Are you sure about the 90 day thing? I was reading a thread here where
Nick Johnson suggested it was a fixed buffer size:
In that case, the person asking seemed to be only able to keep 20
minutes of log data before old logs started to be overwritten (a busy
site I guess!).
Has something changed? Could you check out what the case actually is?
If I might, I'd like to request if log related 'quotas' could be
exposed and published, and expandable with money if possible! :)
They're quite critical to an app I'm trying to plan, and while the
current setup seems to be OK for my needs, the blindness to what's
happening under the covers and what might happen going forward is a
wee bit disconcerting.
Cheers,
> > google-appengi...@googlegroups.com<google-appengine%2Bunsubscrib e...@googlegroups.com>
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.