[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-user
Subject:    RE: Customising Chainsaw
From:       "Milind Rao" <milindr () bellsouth ! net>
Date:       2003-07-30 15:27:34
[Download RAW message or body]

I had just glanced over MDC/NDC in the log4j docs.  I'll go over it again.  Thanks.

On Wed, 30 Jul 2003 08:19:40 -0700, Scott Deboy wrote:

>If you used Chainsaw 2 and defined these extra fields as properties, you
>could filter on them (QuickFilter with a regexp), but sorting would not
>work.  
>
>I like the idea of providing the MDC entries and properties as separate
>columns (comma-delimited name/value pairs are almost less than
>useful)...I'll see what I can do..
>
>I'm also probably going to add the ability to configure how events are
>routed to unique tabs:
>
>Right now, unique combinations of an app and machine (properties with
>pre-defined names) result in the event routed to unique tabs, but I see
>value in allowing someone to choose to route all WARNING, ERROR, DEBUG
>messages to separate tabs instead, or being able to select a property or
>MDC entry as the identifier for routing to unique tabs.
>
>
>-----Original Message-----
>From: Milind Rao [mailto:milindr@bellsouth.net] 
>Sent: Wednesday, July 30, 2003 7:45 AM
>To: Log4J Users List
>Subject: RE: Customising Chainsaw
>
>
>Okay, then I guess I'll have to roll my own since I'd like to see
>different columns for different elements in the message so 
>I can sort and filter the logs based on those elements.  But I'll take a
>look at chainsaw before I start anyway.  Thanks.
>
>On a different note, I hope log4j will start using schemas instead of
>dtds soon.
>
>On Wed, 30 Jul 2003 08:01:25 -0700, Scott Deboy wrote:
>
>>Since Chainsaw supports all of LoggingEvent's capabilities (MDC, 
>>properties, NDC), I would think a transform of this format into log4j's
>
>>dtd would be straightforward if you made the extra fields properties. 
>>Chainsaw could then be used to view the events.  One thing to remember 
>>is that Chainsaw renders properties as a single entry - a 
>>comma-delimited set of name/value pairs (a single field).
>>
>>-----Original Message-----
>>From: Milind Rao [mailto:milindr@bellsouth.net]
>>Sent: Wednesday, July 30, 2003 12:42 AM
>>To: Log4J Users List
>>Subject: Customising Chainsaw 
>>
>>
>>My log message is a complex XML element since there was other 
>>information, such as hardware, message ID, replacement parameters etc. 
>>that I needed in the message.
>>
>>A log file consists of multiple Log message elements.  A Log message 
>>would be something like
>>   <Log>
>>        <Level>Info</Level>
>>        <Date>07-07-2003T12:43</Date>
>>        <Hardware>Camera1</Hardware>
>>        <Source>Tracking</Source>
>>        <MessageID>MSG1023</MessageID>
>>        ...
>>   </Log>
>>
>>To view the logs, I need to have columns for the elements in the log 
>>XML (Hardware, source etc.) instead of one single column for the 
>>message.  Also, level & date would have to be extracted from the Log 
>>XML element.  The message text has to be looked up, based on the 
>>message ID, from a resource file for a locale.
>>
>>I couldn't make out from the Chainsaw home page whether this would be 
>>easy to support/add on to Chainsaw or whether I should just roll my 
>>own.
>>
>>
>>
>>Regards
>>Milind
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: log4j-user-help@jakarta.apache.org
>>
>
>
>
>Regards
>Milind
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-user-help@jakarta.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-user-help@jakarta.apache.org
>



Regards
Milind



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]