I'd also like to see every quota and limit documented, ideally in one
easy to reference spot.
  http://code.google.com/p/googleappengine/issues/detail?id=5677

Also, to go along with that, having a list of quotas your apps hit
logged in some persistent way:
  http://code.google.com/p/googleappengine/issues/detail?id=6296



Robert



On Thu, Jan 19, 2012 at 05:08, Alexis <[email protected]> wrote:
> Hi
>
> We noticed a few days ago that starting from the middle-end of the
> day, a new quota line now appears in one of our app dashboard:
>  "Log Records Received  -  95%  - 946,267 of 1,000,000"
>
> This line is not there in other apps or at the beginning of the day.
> So it must appear only because we are going to reach the quota limit.
> That's fine, but this quota does not appear in the "Quota details"
> section of the dashboard, and is not mentioned in the quotas
> documentation neither in the LogService documentation. In other words
> I have no clue of what is it and could not anticipate it.
>
> We only have an average 15 requests/sec so it's more than 1 million
> requests a day, the quota can't be that we can't log more that 1M
> requests right?
>
> I think it may be linked to the new LogService API that we are
> starting to use. Is it because we read too many records using this
> API?
>
> Can someone shed some light on this? Did I miss something?
> 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 [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to