Hi,
I have a goal for my production-level logging, but I'm not exactly
sure what the correct configuration would be to support that goal.
Currently in development on gwt3.0.3, our config looks like the
following:
<inherits name="com.allen_sauer.gwt.log.gwt-log-OFF" />
<inherits name="com.allen_sauer.gwt.log.gwt-log-RemoteLogger" />
<extend-property name="log_level" values="DEBUG,ERROR"/>
<set-property name="log_DivLogger" value="ENABLED" />
With this, people that want the "production" experience can use the
"normal" URL while people that need trouble-shooting info can add
log_level=ERROR to their URL. When errors occur, the DivLogger
displays, the error gets logged to it and the error gets send to the
server via the RemoteLogger and logged in our server log via log4j.
That's all good.
For our release codeline, I'd still like to have the URL log_level
capability so our customers can use that, as needed, to troubleshoot
an end-user's issue and see error logs in the divlogge, but for the
real production users, I want all the ERRORs to be sent to ther server
without a DivLogger appearing and without the URL being mucked with.
Is it possible to support both these capabilities in a single release
codeline? Basically, I want the server admin's to have visibility in
the server log to when production user's are encountering errors. But
I also don't want to give up on the URL-modification-capability to
display the divlogger. Does that seem like a reasonable approach? Is
this possible?
Hope my questions make sense.
Thanks,
Eric
--
You received this message because you are subscribed to the Google Groups
"gwt-log" 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/gwt-log?hl=en.
