Good point, it's easy to remove the filter if you decided to save all the results.

Want me to look at implementing it, or shall I leave it to the experts?

Cheers,
Stephen



                                                                                       
                                                                                       
                                
                      "Scott Deboy"                                                    
                                                                                       
                                
                      <[EMAIL PROTECTED]        To:       "Log4J Users List" <[EMAIL 
PROTECTED]>                                                                            
                       
                      stems.com>               cc:                                     
                                                                                       
                                
                                               Subject:  RE: save filtered events from 
chainsaw                                                                               
                                
                      20/07/2004 16:16                                                 
                                                                                       
                                
                      Please respond to                                                
                                                                                       
                                
                      "Log4J Users                                                     
                                                                                       
                                
                      List"                                                            
                                                                                       
                                
                                                                                       
                                                                                       
                                
                                                                                       
                                                                                       
                                




Good idea, Stephen

It may be worth having the save always based on the filtered (currently
displayed) events.

Scott

-----Original Message-----
From: Stephen Pain [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 20, 2004 7:51 AM
To: [EMAIL PROTECTED]
Subject: save filtered events from chainsaw


Hi all,

I don't think it's currently possible to do this in chainsaw - please
correct me if I'm wrong... I'd like to be able to use chainsaw to filter
events, and then save those events to a file, but ONLY those events that
were still visible after the filter was applied.

The reason is that I'm regularly loading 50000+ events into chainsaw,
filtering them down to 100-200 events that encapsulate a particular
exception/scenario for further investigation, and then need to send the
relevant info off to someone else so that they can look into it further.
Sending 50MB files around and asking people to search for the bit
they're interested in is a waste of time when I've already done some
preliminary investigation - it would be much better if I could just send
a small, 100% relevant file.

Looking at the code, a change to ChainsawCyclicBufferTableModel +
LogPanel to expose the filteredList directly and then an additional
option in FileSaveAction to switch between getEvents and
getFilteredEvents should be sufficient.

Any thoughts?

Cheers,
Stephen



--

This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.



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






--

This e-mail may contain confidential and/or privileged information. If you are not the 
intended recipient (or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail. Any unauthorized copying, disclosure or 
distribution of the material in this e-mail is strictly forbidden.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to