It should be fine to use Logging for these purposes, so as long as you realize that we will not keep logs around forever. There's a maximum storage limit for storing logs and older entries will be automatically deleted if you cross this limit. I don't know this limit off the top of my head, but for standard logging purposes I haven't heard anyone raise an issue that it wasn't sufficient.
On Sat, Feb 27, 2010 at 11:55 AM, megaswin <[email protected]> wrote: > Hi > > As I understand GAE always logs all incoming requests (ip, agent, > etc). Also an application can use java.util.logging.Logger for > logging app-specific events. Something like that: > > private static final Logger logger = > Logger.getLogger(SearchServlet.class.getName()); > > protected void doPost(HttpServletRequest request, HttpServletResponse > response) > throws ServletException, IOException { > ... > SearchRequest searchRequest = RequestParser.parse(request); > logger.info("searchRequest = " + searchRequest ) > ... > } > > So here is my question : is it ok to use logger.info(...) if number of > requests is quite high? Is there any constraints/quotas? May be will > be better to save such information in database? > > Thanks, > Maxim > > -- > 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]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- 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.
