Properties in Chainsaw are any name/value pair -property- associated with a received event - they are displayed in their own column in the event table.
MDC entries show up as properties in Chainsaw. Any arbitrary name/value pair can be added as properties to events, and MDC is one way to get those properties set (another is the 'application' param on socketappender). In the log4j receivers companion, there is a rewrite appender through which you can add properties to all events processed by an appender: http://logging.apache.org/log4j/companions/receivers/apidocs/org/apache/ log4j/rewrite/package-summary.html In Chainsaw, the documentation mentioning 'PROP.keyname' is shorthand for the name of any property associated with an event. 'application', 'log4jid', 'hostname' and 'log4j.remoteSourceInfo' are the only log4j-provided property names if I recall. application, hostname and log4j.remoteSourceInfo are provided by the network-related appenders. Log4jid is created on the Chainsaw side to support event ordering. Scott Deboy Principal Engineer COMOTIV SYSTEMS 111 SW Columbia Street Ste. 950 Portland, OR 97201 Office: 503.224.7496 Direct Line: 503.821.6482 Cell: 503.997.1367 Fax: 503.222.0185 [EMAIL PROTECTED] www.comotivsystems.com -----Original Message----- From: Jason Tholstrup [mailto:[EMAIL PROTECTED] Sent: Monday, March 03, 2008 12:16 PM To: Log4J Users List Subject: Re: Chainsaw Tab identifier Thanks Scott that was very helpful (and fast). Am I missing the reference to what Prop keyNames are available? It would be nice to know what is available (who knows maybe I'll find something i didn't know i couldn't live without). Even if it's just a matter of looking at the right javadocs that's enough. I'd just like to be able to tinker on my own. Thanks for all your hard work. Chainsaw is pretty cool. Jason Tholstrup Software Engineer [EMAIL PROTECTED] On Mar 3, 2008, at 11:42 AM, Scott Deboy wrote: > Two things: > > 1. To get every socketappender connection to display in its own tab in > Chainsaw, use PROP.log4j.remoteSourceInfo as the tab identifier (note > the log4j. in front of the property name - log4j. isn't some special > property name, that's just the name of the property). > > 2. The 'application' property on socketappender is how you route > events > to different tabs when the two apps are running on the same server and > using socketappender. > > Here's an example of that config: > > <appender name="SOCKET" > class="org.apache.log4j.net.SocketAppender"> > <param name="remoteHost" value="localhost"/> > <param name="LocationInfo" value="true"/> > <param name="port" value="4560"/> > <param name="application" value="someappname"/> > </appender> > > Use a different value in the 'application' param for each of the > socketappender configs and you should be fine. > > > Scott Deboy > Principal Engineer > COMOTIV SYSTEMS > 111 SW Columbia Street Ste. 950 > Portland, OR 97201 > Office: 503.224.7496 > Direct Line: 503.821.6482 > Cell: 503.997.1367 > Fax: 503.222.0185 > [EMAIL PROTECTED] > www.comotivsystems.com > > > -----Original Message----- > From: Jason Tholstrup [mailto:[EMAIL PROTECTED] > Sent: Monday, March 03, 2008 9:24 AM > To: log4j-user@logging.apache.org > Subject: Chainsaw Tab identifier > > Hello, > > I'm trying to figure out what things I need to place in my Tab > identifier field to filter out my applications. I'm using log4j v > 1.2.13 and chainsaw v2. I have two applications running on the same > server and both are using a socketHubAppender on different ports. > > I don't have any location info so the default "PROP.hostName - > PROP.application" only separates by hostname and since I'm running two > apps on the same server I get both logs dumped to the same tab. I've > tried adding PROP.remoteSourceInfo (since that is a column in the logs > that shows up and has the port number listed) and that property > appears to return nothing. It's my understanding that the location > info does not work in log4j 1.2.X. So my question is two fold. Is > there some reference that I can look at that will tell me what > properties are available, and can someone tell me how I would go about > doing this? I see in the comments for LoggingEventFieldResolver the > following field are available but nothing here seems like it will work > for me. Plus there seems to be no explanation of what keyName is in > PROP.keyName. > > * Field Name Field value (String > representation Return type > * LOGGER category name > (logger) String > * LEVEL > level Level > * CLASS locationInformation's class > name String > * FILE locationInformation's file > name String > * LINE locationInformation's line > number String > * METHOD locationInformation's method > name String > * MSG > message Object > * NDC > NDC String > * EXCEPTION throwable string > representation ThrowableInformation > * TIMESTAMP > timestamp Long > * THREAD > thread String > * PROP.keyName entry in the Property > hashtable String > * mapped to the key [keyName] > > > Any help would be appreciated. > > Jason Tholstrup > > > > > > --------------------------------------------------------------------- > 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] > --------------------------------------------------------------------- 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]
