There is a default 'tab identifier' which controls how events are initially 
routed to tabs.  This tab identifier relies on the expression syntax keywords 
(see the tutorial).

For example, to have events route to a tab based on level (all WARN events end 
up on a common tab, all INFO events end up on a common tab, etc), use the tab 
identifier LEVEL.

The default tab identifier routes events based on a combination of the 
application name (if provided) and host name.

ChainsawAppenderHandler is the class that processes events received by any 
receiver and forwards the events to the appropriate tab.  See getTabIdentifier 
method and the inner class WorkerThread's dispatchEventBatch method.

http://cvs.apache.org/viewcvs.cgi/logging-chainsaw/src/java/org/apache/log4j/chainsaw/ChainsawAppenderHandler.java?rev=1.28&view=markup

Scott

-----Original Message-----
From:   Tan Kah Siong [mailto:[EMAIL PROTECTED]
Sent:   Mon 6/27/2005 12:58 AM
To:     Log4J Users List
Cc:     
Subject:        Tabs of Chainsaw
Hi,

I am trying to patch a some parts of the receiver
(file pattern and db) to suit some of my requirements.


I have the following enquiries on how the LoggingEvent
work.

I wish to know what determines the tab when chainsaw
is running. I am trying to parse a xml lite file by
making some decoder changes to LogFilePatternReceiver
class. My way was to directly manipulate the file and
place all the names fields and values into CurrentMap.

The changes seems to work except that on every new
line of  log, a new tab pops up in chainsaw, thus the
question on what determines the tab. My gut feeling
tells me its in the LoggingEvent class, but i cannot
find any info on my problem based on that class.

Please advice. 


                
____________________________________________________ 
Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
http://football.fantasysports.yahoo.com

---------------------------------------------------------------------
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]

Reply via email to