Hello, We're trying to add a handler to the root logger, which seems to work in dev, but, doesn't work in live. Our specific use case is that we are trying to add a Handler to facilitate sending log messages of a particular level to a remote log aggregation service.
Has anyone had success in adding a handler to the root logger? If so, could you please detail your experience. We have tried things like: * Adding directly to the root logger through static initialization in Guice. This works in dev but gets a security exception (LoggingPermission) in live. * Various combinations of AOP. * Using logging.properties to explicitly define the logger. This was the most promising lead and actually seemed to be working, but, ultimately suffered the same problematic fate. We're currently exploring mitigation options like a logging facade (SLF4J or possibly just subclassing Logger), but, this has a host of obvious problems (no support for 3rd party libraries etc). Another option is to potentially try and use the admin logging console. If pertinent our app stack is GWT on Guice. Also, if we're lucky enough to have someone from the Google GAE team look at this it would be terrific to understand a little bit about the technical detail of logging for java in GAE. There is a reasonable amount of conflicting information around the web which has resulted in a lot of burnt time. An authoritative view would be very helpful and of obvious benefit when trying to design these types of solutions. Regards, - Andrew. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
