There wasn't as much thought behind it as the fairly cool name would
imply. Basically, if you had a hierarchy of loggers derived from
"metrics" and a hierarchy of logger for diagnostics, you could do
something like:
<log4j:configuration>
<logger name="metrics">
<level value="INFO"/>
<appender-ref ref="metrics-log"/>
</logger>
<logger name="com.example.foobar">
<level value="INFO"/>
<appender-ref ref="foobar-log"/>
</logger>
<logger name="metrics.com.example.foobar">
<level value="INFO"/>
<appender-ref ref="foobar-log"/>
</logger>
</log4j:configuration>
On Jan 20, 2005, at 10:51 AM, Daniel Einspanjer wrote:
Curt,
Could you provide any more information on this concept of "bridging
loggers" by routing to the same appenders? It sounds like a tactic
that might be useful to me, and I haven't seen this mentioned anywhere
else yet.
On Wed, 19 Jan 2005 16:38:16 -0600, Curt Arnold <[EMAIL PROTECTED]>
wrote:
One problem is when a message is of interest to multiple audiences.
For example, the search metrics may be of interest to both the
diagnostician and the performance analyst. Since these would
typically
be low volume, it might be simplest just to repeat the message on both
the diagnostic and performance logger. Otherwise, you might be able
to
bridge loggers by routing "performance.com.example.foobar" to the same
appenders as "com.example.foobar".
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
