Hi Scott,
Glad to hear you like it -
MDC and the PROP keyword were consolidated
If you change the tab identifier to PROP.server.name, it should work.
Let us know if this doesn't work or if you have other questions.
Scott
-----Original Message-----
From: Scott Heaberlin [mailto:heab...@yahoo.com]
Sent: Thursday, June 24, 2004 7:30 AM
To: log4...@logging.apache.org
Subject: Chainsaw v2 tab names
It has been a while since I've built chainsaw v2 from
cvs...
I updated and built it again today, only to notice
that my tab names now display the literal string I
specified in the "Application-wide Preferences" dialog
for "Tab identifier."
Previously, I used:
MDC.server.name
to name tabs based on an MDC value we place in all our
logging events. This allowed me previously to have
multiple servers sending logging events to the same
socket receiver. This worked wonderfully as a
workaround for what I believed to be an issue with
whatever property 1.2.8's SocketAppender was setting
in outbound LoggingEvents, as somewhere along the line
of building chainsaw2 from cvs all my remote logging
started showing up on the same tab. We already had
the MDC "server.name" in place, so the "Tab
identifier" feature was extremely handy.
Now, I have a tab literally named "MDC.server.name"
instead of tabs named "serverA", "serverB", "serverC",
etc.
Any help would be appreciated. Chainsaw rules, by the
way. I am reading up now about the log tailing
plugin... it sounds awesome, especially for
environments like mine where developers are given
read-only access to production logs.
Keep up the good work!
3 messages in org.apache.logging.log4j-userRE: Chainsaw v2 tab names
