You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Florian Boulay <fl...@gmail.com> on 2010/07/23 18:15:21 UTC
problem using Chainsaw, "found non matching line"
Hello,
Since 2 days, I am trying to configure Chainsaw v2 for parsing my log4j log
files, but it always returns "found non matching line...".
Here is my log4j configuration :
<appender name="crm" class="org.apache.log4j.DailyRollingFileAppender">
....
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="[%d{dd MMM yyyy
HH:mm:ss,SSS}] [%p] user: [%x] %c | %m%n"/>
</layout>
</appender>
And my Chainsaw configuration :
<plugin name="logFileReceiver"
class="org.apache.log4j.varia.LogFilePatternReceiver">
<param name="fileURL" value="file:///c:/app.log" />
<param name="timestampFormat" value="dd MMM yyyy HH:mm:ss,SSS"/>
<param name="logFormat" value="[TIMESTAMP] [LEVEL] user: [*] * |
MESSAGE"/>
<param name="name" value="log app" />
<param name="tailing" value="true" />
</plugin>
It does not work. I tried a lot of logFormat, but I do not manage to get it
work. Can someone help me ?
Thanks
Re: problem using Chainsaw, "found non matching line"
Posted by Florian Boulay <fl...@gmail.com>.
If course I will try the new version as soon as I can. I will give you a
feedback in a few days.
Le 23 juil. 2010 18:49, "Scott Deboy" <sc...@gmail.com> a écrit :
Glad to help..
If you have an interest/ability in trying out the latest version of
Chainsaw, there are a lot of new features (and some improvements to
VFSLogFilePatternReceiver).
I've uploaded a build of the standalone.zip and a screen video to
http://people.apache.org/~sdeboy/
See the release notes (in the help menu) for a list of features that have
been added (note there's now a thumbnail bar on the right w/colors, and the
marker field is editable so notes can be added to events).
Interested in any feedback folks want to provide...
Scott
On Fri, Jul 23, 2010 at 9:38 AM, Florian Boulay <florian.boulay@gmail.com
>wrote:
> Thanks for your quick answer ! I will try on Monday.
>
> Le 23 juil. 2010 18:29, "Scott Deboy" <s...
Re: problem using Chainsaw, "found non matching line"
Posted by Scott Deboy <sc...@gmail.com>.
Glad to help..
If you have an interest/ability in trying out the latest version of
Chainsaw, there are a lot of new features (and some improvements to
VFSLogFilePatternReceiver).
I've uploaded a build of the standalone.zip and a screen video to
http://people.apache.org/~sdeboy/
See the release notes (in the help menu) for a list of features that have
been added (note there's now a thumbnail bar on the right w/colors, and the
marker field is editable so notes can be added to events).
Interested in any feedback folks want to provide...
Scott
On Fri, Jul 23, 2010 at 9:38 AM, Florian Boulay <fl...@gmail.com>wrote:
> Thanks for your quick answer ! I will try on Monday.
>
> Le 23 juil. 2010 18:29, "Scott Deboy" <sc...@gmail.com> a écrit :
>
> Try:
> [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
>
> Or, if you don't want the user property defined (you probably still want
> the
> logger, yes?)
> [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
>
>
> On Fri, Jul 23, 2010 at 9:15 AM, Florian Boulay <florian.boulay@gmail.com
> >wrote:
>
>
> > Hello,
> >
> > Since 2 days, I am trying to configure Chainsaw v2 for parsing my log4j
> log
> > files, b...
>
Re: problem using Chainsaw, "found non matching line"
Posted by Florian Boulay <fl...@gmail.com>.
Thanks for your quick answer ! I will try on Monday.
Le 23 juil. 2010 18:29, "Scott Deboy" <sc...@gmail.com> a écrit :
Try:
[TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
Or, if you don't want the user property defined (you probably still want the
logger, yes?)
[TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
On Fri, Jul 23, 2010 at 9:15 AM, Florian Boulay <florian.boulay@gmail.com
>wrote:
> Hello,
>
> Since 2 days, I am trying to configure Chainsaw v2 for parsing my log4j
log
> files, b...
Re: problem using Chainsaw, "found non matching line"
Posted by Florian Boulay <f....@gmail.com>.
Thanks Scott, The last fix does correct the problem. I did not know that the
dot in the month was specific to the French locale. Hope this fix will be
useful for other locale too.
2010/7/29 Scott Deboy <sc...@gmail.com>
> Florian's locale is French, so simpledateformat is constructing timestamps
> with a dot in the month, which the regular expression wasn't taking into
> account in LogFilePatternReceiver...I've committed a fix to the receivers
> companion in svn 980277 and I've uploaded a version of Chainsaw with the
> fix
> to http://people.apache.org/~sdeboy/ <http://people.apache.org/%7Esdeboy/>
>
> Feedback appreciated.
>
> Scott
>
> On Tue, Jul 27, 2010 at 1:36 AM, Florian Boulay <f.mail.list@gmail.com
> >wrote:
>
> > Hi Scott,
> >
> > Thnaks for finding this bug, but unfortunately the last release does not
> > fix
> > the issue. I tried with a LogFilePatternReceiver and with theses 2
> formats
> > :
> > - [TIMESTAMP] [LEVEL] user: [PROP(*)] LOGGER | MESSAGE
> > - [TIMESTAMP] [LEVEL] user: [PROP(USER)] LOGGER | MESSAGE
> >
> > Another bug : when loading the Chainsaw config file the parameter "name"
> > (<param name="name" value="App Dev"/>) does not seem to considered.
> Instead
> > the name of the displayed receiver is "logFileReceiver".
> >
> > I am still searching why this does not work.
> >
> > 2010/7/27 Scott Deboy <sc...@gmail.com>
> >
> > > I've committed a fix to the regexp building logic to correctly escape
> > > regexp
> > > characters (including the pipe character) in svn 979552.
> > >
> > > I've also uploaded a new chainsaw standalone.zip to
> > > http://people.apache.org/~sdeboy/<http://people.apache.org/%7Esdeboy/><
> http://people.apache.org/%7Esdeboy/><
> > http://people.apache.org/%7Esdeboy/>
> > >
> > > I was able to parse a log file with your provided patternlayout using:
> > >
> > > <param name="timestampFormat" value="dd MMM yyyy HH:mm:ss,SSS"/>
> > > <param name="logFormat" value="[TIMESTAMP] [LEVEL] user:
> > [PROP(USER)]
> > > LOGGER | MESSAGE"/>
> > >
> > > I also tested greater than and less than symbols as delimiters and they
> > > work
> > > fine, but you have to use a layout which uses the encoded symbols in
> the
> > > xml
> > > config file:
> > >
> > > <param name="logFormat" value="<TIMESTAMP> <LEVEL>
> > user:
> > > <PROP(USER)> LOGGER | MESSAGE"/>
> > >
> > > You may want to use
> > org.apache.log4j.chainsaw.vfs.VFSLogFilePatternReceiver
> > > instead - it more reliably tails, and can tail files using any of the
> > file
> > > systems supported by Jakarta Commons-VFS (including tailing over ssh).
> > > Changing the receiver class name should be all you need to do to use
> it..
> > >
> > > Let me know if the latest standalone zip file works for you.
> > >
> > > Scott
> > >
> > > On Mon, Jul 26, 2010 at 1:55 AM, Florian Boulay <
> > florian.boulay@gmail.com
> > > >wrote:
> > >
> > > > When using the format *[TIMESTAMP] **, the updated version of
> Chainsaw
> > > > manages to parse 4 lines of my log file. The old version does not
> > manage
> > > to
> > > > do it.
> > > > However the *** get a lot of lines ! It does not stop when it
> > encounters
> > > a
> > > > \r\n
> > > >
> > > > 2010/7/26 Florian Boulay <fl...@gmail.com>
> > > >
> > > > > Ok I answered to quickly. The updated version still parses my log
> > file,
> > > > but
> > > > > it always display : "found non matching line:..."
> > > > >
> > > > > 2010/7/26 Florian Boulay <fl...@gmail.com>
> > > > >
> > > > > Hi,
> > > > >>
> > > > >> I tried the format [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE with the
> > > > >> official version of Chainsaw and the updated version found here :
> > > > >> http://people.apache.org/~sdeboy/<http://people.apache.org/%7Esdeboy/>
> <http://people.apache.org/%7Esdeboy/>
> > <http://people.apache.org/%7Esdeboy/><
> > > http://people.apache.org/%7Esdeboy/><
> > > > http://people.apache.org/%7Esdeboy/>and It did not work.
> > > > >>
> > > > >> On the updated version, nothing happen when choosing my chainsaw
> > confg
> > > > >> file. No error message in the tab "chainsaw-log". Sound like it
> did
> > > not
> > > > >> parse any file. I also tried to delete all files in my .chainsaw
> > > > directory,
> > > > >> but it does not change the behavior of Chainsaw. Maybe I should
> try
> > > with
> > > > a
> > > > >> SocketAppender instead of loading a local file.
> > > > >>
> > > > >> 2010/7/26 Scott Deboy <sc...@gmail.com>
> > > > >>
> > > > >> Can you try
> > > > >>> [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE
> > > > >>>
> > > > >>> Also, try the updated version of Chainsaw when you have a chance
> > and
> > > > see
> > > > >>> if that resolves your issue.
> > > > >>>
> > > > >>> Scott
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> On Jul 26, 2010, at 12:25 AM, Florian Boulay <
> > > florian.boulay@gmail.com
> > > > >
> > > > >>> wrote:
> > > > >>>
> > > > >>> Hello,
> > > > >>>>
> > > > >>>> These two formats do not work :
> > > > >>>> - [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
> > > > >>>> - [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
> > > > >>>>
> > > > >>>> I am still searching the right format, I tried just '*' and it
> > still
> > > > >>>> does
> > > > >>>> not work....
> > > > >>>>
> > > > >>>> 2010/7/23 Scott Deboy <sc...@gmail.com>
> > > > >>>>
> > > > >>>> Try:
> > > > >>>>> [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
> > > > >>>>>
> > > > >>>>> Or, if you don't want the user property defined (you probably
> > still
> > > > >>>>> want
> > > > >>>>> the
> > > > >>>>> logger, yes?)
> > > > >>>>> [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> On Fri, Jul 23, 2010 at 9:15 AM, Florian Boulay <
> > > > >>>>> florian.boulay@gmail.com
> > > > >>>>>
> > > > >>>>>> wrote:
> > > > >>>>>>
> > > > >>>>>
> > > > >>>>> Hello,
> > > > >>>>>>
> > > > >>>>>> Since 2 days, I am trying to configure Chainsaw v2 for parsing
> > my
> > > > >>>>>> log4j
> > > > >>>>>>
> > > > >>>>> log
> > > > >>>>>
> > > > >>>>>> files, but it always returns "found non matching line...".
> > > > >>>>>>
> > > > >>>>>> Here is my log4j configuration :
> > > > >>>>>> <appender name="crm"
> > > > >>>>>> class="org.apache.log4j.DailyRollingFileAppender">
> > > > >>>>>> ....
> > > > >>>>>> <layout class="org.apache.log4j.PatternLayout">
> > > > >>>>>> <param name="ConversionPattern" value="[%d{dd MMM
> yyyy
> > > > >>>>>> HH:mm:ss,SSS}] [%p] user: [%x] %c | %m%n"/>
> > > > >>>>>> </layout>
> > > > >>>>>> </appender>
> > > > >>>>>>
> > > > >>>>>> And my Chainsaw configuration :
> > > > >>>>>> <plugin name="logFileReceiver"
> > > > >>>>>> class="org.apache.log4j.varia.LogFilePatternReceiver">
> > > > >>>>>> <param name="fileURL" value="file:///c:/app.log" />
> > > > >>>>>> <param name="timestampFormat" value="dd MMM yyyy
> > > > HH:mm:ss,SSS"/>
> > > > >>>>>> <param name="logFormat" value="[TIMESTAMP] [LEVEL] user:
> > [*]
> > > *
> > > > |
> > > > >>>>>> MESSAGE"/>
> > > > >>>>>> <param name="name" value="log app" />
> > > > >>>>>> <param name="tailing" value="true" />
> > > > >>>>>> </plugin>
> > > > >>>>>>
> > > > >>>>>> It does not work. I tried a lot of logFormat, but I do not
> > manage
> > > to
> > > > >>>>>> get
> > > > >>>>>>
> > > > >>>>> it
> > > > >>>>>
> > > > >>>>>> work. Can someone help me ?
> > > > >>>>>>
> > > > >>>>>> Thanks
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>
> > > > >>>
> > ---------------------------------------------------------------------
> > > > >>> To unsubscribe, e-mail:
> log4j-user-unsubscribe@logging.apache.org
> > > > >>> For additional commands, e-mail:
> > log4j-user-help@logging.apache.org
> > > > >>>
> > > > >>>
> > > > >>
> > > > >
> > > >
> > >
> >
>
Re: problem using Chainsaw, "found non matching line"
Posted by Scott Deboy <sc...@gmail.com>.
Florian's locale is French, so simpledateformat is constructing timestamps
with a dot in the month, which the regular expression wasn't taking into
account in LogFilePatternReceiver...I've committed a fix to the receivers
companion in svn 980277 and I've uploaded a version of Chainsaw with the fix
to http://people.apache.org/~sdeboy/
Feedback appreciated.
Scott
On Tue, Jul 27, 2010 at 1:36 AM, Florian Boulay <f....@gmail.com>wrote:
> Hi Scott,
>
> Thnaks for finding this bug, but unfortunately the last release does not
> fix
> the issue. I tried with a LogFilePatternReceiver and with theses 2 formats
> :
> - [TIMESTAMP] [LEVEL] user: [PROP(*)] LOGGER | MESSAGE
> - [TIMESTAMP] [LEVEL] user: [PROP(USER)] LOGGER | MESSAGE
>
> Another bug : when loading the Chainsaw config file the parameter "name"
> (<param name="name" value="App Dev"/>) does not seem to considered. Instead
> the name of the displayed receiver is "logFileReceiver".
>
> I am still searching why this does not work.
>
> 2010/7/27 Scott Deboy <sc...@gmail.com>
>
> > I've committed a fix to the regexp building logic to correctly escape
> > regexp
> > characters (including the pipe character) in svn 979552.
> >
> > I've also uploaded a new chainsaw standalone.zip to
> > http://people.apache.org/~sdeboy/ <http://people.apache.org/%7Esdeboy/><
> http://people.apache.org/%7Esdeboy/>
> >
> > I was able to parse a log file with your provided patternlayout using:
> >
> > <param name="timestampFormat" value="dd MMM yyyy HH:mm:ss,SSS"/>
> > <param name="logFormat" value="[TIMESTAMP] [LEVEL] user:
> [PROP(USER)]
> > LOGGER | MESSAGE"/>
> >
> > I also tested greater than and less than symbols as delimiters and they
> > work
> > fine, but you have to use a layout which uses the encoded symbols in the
> > xml
> > config file:
> >
> > <param name="logFormat" value="<TIMESTAMP> <LEVEL>
> user:
> > <PROP(USER)> LOGGER | MESSAGE"/>
> >
> > You may want to use
> org.apache.log4j.chainsaw.vfs.VFSLogFilePatternReceiver
> > instead - it more reliably tails, and can tail files using any of the
> file
> > systems supported by Jakarta Commons-VFS (including tailing over ssh).
> > Changing the receiver class name should be all you need to do to use it..
> >
> > Let me know if the latest standalone zip file works for you.
> >
> > Scott
> >
> > On Mon, Jul 26, 2010 at 1:55 AM, Florian Boulay <
> florian.boulay@gmail.com
> > >wrote:
> >
> > > When using the format *[TIMESTAMP] **, the updated version of Chainsaw
> > > manages to parse 4 lines of my log file. The old version does not
> manage
> > to
> > > do it.
> > > However the *** get a lot of lines ! It does not stop when it
> encounters
> > a
> > > \r\n
> > >
> > > 2010/7/26 Florian Boulay <fl...@gmail.com>
> > >
> > > > Ok I answered to quickly. The updated version still parses my log
> file,
> > > but
> > > > it always display : "found non matching line:..."
> > > >
> > > > 2010/7/26 Florian Boulay <fl...@gmail.com>
> > > >
> > > > Hi,
> > > >>
> > > >> I tried the format [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE with the
> > > >> official version of Chainsaw and the updated version found here :
> > > >> http://people.apache.org/~sdeboy/<http://people.apache.org/%7Esdeboy/>
> <http://people.apache.org/%7Esdeboy/><
> > http://people.apache.org/%7Esdeboy/><
> > > http://people.apache.org/%7Esdeboy/>and It did not work.
> > > >>
> > > >> On the updated version, nothing happen when choosing my chainsaw
> confg
> > > >> file. No error message in the tab "chainsaw-log". Sound like it did
> > not
> > > >> parse any file. I also tried to delete all files in my .chainsaw
> > > directory,
> > > >> but it does not change the behavior of Chainsaw. Maybe I should try
> > with
> > > a
> > > >> SocketAppender instead of loading a local file.
> > > >>
> > > >> 2010/7/26 Scott Deboy <sc...@gmail.com>
> > > >>
> > > >> Can you try
> > > >>> [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE
> > > >>>
> > > >>> Also, try the updated version of Chainsaw when you have a chance
> and
> > > see
> > > >>> if that resolves your issue.
> > > >>>
> > > >>> Scott
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>> On Jul 26, 2010, at 12:25 AM, Florian Boulay <
> > florian.boulay@gmail.com
> > > >
> > > >>> wrote:
> > > >>>
> > > >>> Hello,
> > > >>>>
> > > >>>> These two formats do not work :
> > > >>>> - [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
> > > >>>> - [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
> > > >>>>
> > > >>>> I am still searching the right format, I tried just '*' and it
> still
> > > >>>> does
> > > >>>> not work....
> > > >>>>
> > > >>>> 2010/7/23 Scott Deboy <sc...@gmail.com>
> > > >>>>
> > > >>>> Try:
> > > >>>>> [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
> > > >>>>>
> > > >>>>> Or, if you don't want the user property defined (you probably
> still
> > > >>>>> want
> > > >>>>> the
> > > >>>>> logger, yes?)
> > > >>>>> [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
> > > >>>>>
> > > >>>>>
> > > >>>>> On Fri, Jul 23, 2010 at 9:15 AM, Florian Boulay <
> > > >>>>> florian.boulay@gmail.com
> > > >>>>>
> > > >>>>>> wrote:
> > > >>>>>>
> > > >>>>>
> > > >>>>> Hello,
> > > >>>>>>
> > > >>>>>> Since 2 days, I am trying to configure Chainsaw v2 for parsing
> my
> > > >>>>>> log4j
> > > >>>>>>
> > > >>>>> log
> > > >>>>>
> > > >>>>>> files, but it always returns "found non matching line...".
> > > >>>>>>
> > > >>>>>> Here is my log4j configuration :
> > > >>>>>> <appender name="crm"
> > > >>>>>> class="org.apache.log4j.DailyRollingFileAppender">
> > > >>>>>> ....
> > > >>>>>> <layout class="org.apache.log4j.PatternLayout">
> > > >>>>>> <param name="ConversionPattern" value="[%d{dd MMM yyyy
> > > >>>>>> HH:mm:ss,SSS}] [%p] user: [%x] %c | %m%n"/>
> > > >>>>>> </layout>
> > > >>>>>> </appender>
> > > >>>>>>
> > > >>>>>> And my Chainsaw configuration :
> > > >>>>>> <plugin name="logFileReceiver"
> > > >>>>>> class="org.apache.log4j.varia.LogFilePatternReceiver">
> > > >>>>>> <param name="fileURL" value="file:///c:/app.log" />
> > > >>>>>> <param name="timestampFormat" value="dd MMM yyyy
> > > HH:mm:ss,SSS"/>
> > > >>>>>> <param name="logFormat" value="[TIMESTAMP] [LEVEL] user:
> [*]
> > *
> > > |
> > > >>>>>> MESSAGE"/>
> > > >>>>>> <param name="name" value="log app" />
> > > >>>>>> <param name="tailing" value="true" />
> > > >>>>>> </plugin>
> > > >>>>>>
> > > >>>>>> It does not work. I tried a lot of logFormat, but I do not
> manage
> > to
> > > >>>>>> get
> > > >>>>>>
> > > >>>>> it
> > > >>>>>
> > > >>>>>> work. Can someone help me ?
> > > >>>>>>
> > > >>>>>> Thanks
> > > >>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>
> ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > > >>> For additional commands, e-mail:
> log4j-user-help@logging.apache.org
> > > >>>
> > > >>>
> > > >>
> > > >
> > >
> >
>
Re: problem using Chainsaw, "found non matching line"
Posted by Florian Boulay <f....@gmail.com>.
Hi Scott,
Thnaks for finding this bug, but unfortunately the last release does not fix
the issue. I tried with a LogFilePatternReceiver and with theses 2 formats :
- [TIMESTAMP] [LEVEL] user: [PROP(*)] LOGGER | MESSAGE
- [TIMESTAMP] [LEVEL] user: [PROP(USER)] LOGGER | MESSAGE
Another bug : when loading the Chainsaw config file the parameter "name"
(<param name="name" value="App Dev"/>) does not seem to considered. Instead
the name of the displayed receiver is "logFileReceiver".
I am still searching why this does not work.
2010/7/27 Scott Deboy <sc...@gmail.com>
> I've committed a fix to the regexp building logic to correctly escape
> regexp
> characters (including the pipe character) in svn 979552.
>
> I've also uploaded a new chainsaw standalone.zip to
> http://people.apache.org/~sdeboy/ <http://people.apache.org/%7Esdeboy/>
>
> I was able to parse a log file with your provided patternlayout using:
>
> <param name="timestampFormat" value="dd MMM yyyy HH:mm:ss,SSS"/>
> <param name="logFormat" value="[TIMESTAMP] [LEVEL] user: [PROP(USER)]
> LOGGER | MESSAGE"/>
>
> I also tested greater than and less than symbols as delimiters and they
> work
> fine, but you have to use a layout which uses the encoded symbols in the
> xml
> config file:
>
> <param name="logFormat" value="<TIMESTAMP> <LEVEL> user:
> <PROP(USER)> LOGGER | MESSAGE"/>
>
> You may want to use org.apache.log4j.chainsaw.vfs.VFSLogFilePatternReceiver
> instead - it more reliably tails, and can tail files using any of the file
> systems supported by Jakarta Commons-VFS (including tailing over ssh).
> Changing the receiver class name should be all you need to do to use it..
>
> Let me know if the latest standalone zip file works for you.
>
> Scott
>
> On Mon, Jul 26, 2010 at 1:55 AM, Florian Boulay <florian.boulay@gmail.com
> >wrote:
>
> > When using the format *[TIMESTAMP] **, the updated version of Chainsaw
> > manages to parse 4 lines of my log file. The old version does not manage
> to
> > do it.
> > However the *** get a lot of lines ! It does not stop when it encounters
> a
> > \r\n
> >
> > 2010/7/26 Florian Boulay <fl...@gmail.com>
> >
> > > Ok I answered to quickly. The updated version still parses my log file,
> > but
> > > it always display : "found non matching line:..."
> > >
> > > 2010/7/26 Florian Boulay <fl...@gmail.com>
> > >
> > > Hi,
> > >>
> > >> I tried the format [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE with the
> > >> official version of Chainsaw and the updated version found here :
> > >> http://people.apache.org/~sdeboy/<http://people.apache.org/%7Esdeboy/><
> http://people.apache.org/%7Esdeboy/><
> > http://people.apache.org/%7Esdeboy/>and It did not work.
> > >>
> > >> On the updated version, nothing happen when choosing my chainsaw confg
> > >> file. No error message in the tab "chainsaw-log". Sound like it did
> not
> > >> parse any file. I also tried to delete all files in my .chainsaw
> > directory,
> > >> but it does not change the behavior of Chainsaw. Maybe I should try
> with
> > a
> > >> SocketAppender instead of loading a local file.
> > >>
> > >> 2010/7/26 Scott Deboy <sc...@gmail.com>
> > >>
> > >> Can you try
> > >>> [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE
> > >>>
> > >>> Also, try the updated version of Chainsaw when you have a chance and
> > see
> > >>> if that resolves your issue.
> > >>>
> > >>> Scott
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> On Jul 26, 2010, at 12:25 AM, Florian Boulay <
> florian.boulay@gmail.com
> > >
> > >>> wrote:
> > >>>
> > >>> Hello,
> > >>>>
> > >>>> These two formats do not work :
> > >>>> - [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
> > >>>> - [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
> > >>>>
> > >>>> I am still searching the right format, I tried just '*' and it still
> > >>>> does
> > >>>> not work....
> > >>>>
> > >>>> 2010/7/23 Scott Deboy <sc...@gmail.com>
> > >>>>
> > >>>> Try:
> > >>>>> [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
> > >>>>>
> > >>>>> Or, if you don't want the user property defined (you probably still
> > >>>>> want
> > >>>>> the
> > >>>>> logger, yes?)
> > >>>>> [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
> > >>>>>
> > >>>>>
> > >>>>> On Fri, Jul 23, 2010 at 9:15 AM, Florian Boulay <
> > >>>>> florian.boulay@gmail.com
> > >>>>>
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>
> > >>>>> Hello,
> > >>>>>>
> > >>>>>> Since 2 days, I am trying to configure Chainsaw v2 for parsing my
> > >>>>>> log4j
> > >>>>>>
> > >>>>> log
> > >>>>>
> > >>>>>> files, but it always returns "found non matching line...".
> > >>>>>>
> > >>>>>> Here is my log4j configuration :
> > >>>>>> <appender name="crm"
> > >>>>>> class="org.apache.log4j.DailyRollingFileAppender">
> > >>>>>> ....
> > >>>>>> <layout class="org.apache.log4j.PatternLayout">
> > >>>>>> <param name="ConversionPattern" value="[%d{dd MMM yyyy
> > >>>>>> HH:mm:ss,SSS}] [%p] user: [%x] %c | %m%n"/>
> > >>>>>> </layout>
> > >>>>>> </appender>
> > >>>>>>
> > >>>>>> And my Chainsaw configuration :
> > >>>>>> <plugin name="logFileReceiver"
> > >>>>>> class="org.apache.log4j.varia.LogFilePatternReceiver">
> > >>>>>> <param name="fileURL" value="file:///c:/app.log" />
> > >>>>>> <param name="timestampFormat" value="dd MMM yyyy
> > HH:mm:ss,SSS"/>
> > >>>>>> <param name="logFormat" value="[TIMESTAMP] [LEVEL] user: [*]
> *
> > |
> > >>>>>> MESSAGE"/>
> > >>>>>> <param name="name" value="log app" />
> > >>>>>> <param name="tailing" value="true" />
> > >>>>>> </plugin>
> > >>>>>>
> > >>>>>> It does not work. I tried a lot of logFormat, but I do not manage
> to
> > >>>>>> get
> > >>>>>>
> > >>>>> it
> > >>>>>
> > >>>>>> work. Can someone help me ?
> > >>>>>>
> > >>>>>> Thanks
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > >>> For additional commands, e-mail: log4j-user-help@logging.apache.org
> > >>>
> > >>>
> > >>
> > >
> >
>
Re: problem using Chainsaw, "found non matching line"
Posted by Scott Deboy <sc...@gmail.com>.
I've committed a fix to the regexp building logic to correctly escape regexp
characters (including the pipe character) in svn 979552.
I've also uploaded a new chainsaw standalone.zip to
http://people.apache.org/~sdeboy/
I was able to parse a log file with your provided patternlayout using:
<param name="timestampFormat" value="dd MMM yyyy HH:mm:ss,SSS"/>
<param name="logFormat" value="[TIMESTAMP] [LEVEL] user: [PROP(USER)]
LOGGER | MESSAGE"/>
I also tested greater than and less than symbols as delimiters and they work
fine, but you have to use a layout which uses the encoded symbols in the xml
config file:
<param name="logFormat" value="<TIMESTAMP> <LEVEL> user:
<PROP(USER)> LOGGER | MESSAGE"/>
You may want to use org.apache.log4j.chainsaw.vfs.VFSLogFilePatternReceiver
instead - it more reliably tails, and can tail files using any of the file
systems supported by Jakarta Commons-VFS (including tailing over ssh).
Changing the receiver class name should be all you need to do to use it..
Let me know if the latest standalone zip file works for you.
Scott
On Mon, Jul 26, 2010 at 1:55 AM, Florian Boulay <fl...@gmail.com>wrote:
> When using the format *[TIMESTAMP] **, the updated version of Chainsaw
> manages to parse 4 lines of my log file. The old version does not manage to
> do it.
> However the *** get a lot of lines ! It does not stop when it encounters a
> \r\n
>
> 2010/7/26 Florian Boulay <fl...@gmail.com>
>
> > Ok I answered to quickly. The updated version still parses my log file,
> but
> > it always display : "found non matching line:..."
> >
> > 2010/7/26 Florian Boulay <fl...@gmail.com>
> >
> > Hi,
> >>
> >> I tried the format [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE with the
> >> official version of Chainsaw and the updated version found here :
> >> http://people.apache.org/~sdeboy/ <http://people.apache.org/%7Esdeboy/><
> http://people.apache.org/%7Esdeboy/>and It did not work.
> >>
> >> On the updated version, nothing happen when choosing my chainsaw confg
> >> file. No error message in the tab "chainsaw-log". Sound like it did not
> >> parse any file. I also tried to delete all files in my .chainsaw
> directory,
> >> but it does not change the behavior of Chainsaw. Maybe I should try with
> a
> >> SocketAppender instead of loading a local file.
> >>
> >> 2010/7/26 Scott Deboy <sc...@gmail.com>
> >>
> >> Can you try
> >>> [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE
> >>>
> >>> Also, try the updated version of Chainsaw when you have a chance and
> see
> >>> if that resolves your issue.
> >>>
> >>> Scott
> >>>
> >>>
> >>>
> >>>
> >>> On Jul 26, 2010, at 12:25 AM, Florian Boulay <florian.boulay@gmail.com
> >
> >>> wrote:
> >>>
> >>> Hello,
> >>>>
> >>>> These two formats do not work :
> >>>> - [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
> >>>> - [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
> >>>>
> >>>> I am still searching the right format, I tried just '*' and it still
> >>>> does
> >>>> not work....
> >>>>
> >>>> 2010/7/23 Scott Deboy <sc...@gmail.com>
> >>>>
> >>>> Try:
> >>>>> [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
> >>>>>
> >>>>> Or, if you don't want the user property defined (you probably still
> >>>>> want
> >>>>> the
> >>>>> logger, yes?)
> >>>>> [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
> >>>>>
> >>>>>
> >>>>> On Fri, Jul 23, 2010 at 9:15 AM, Florian Boulay <
> >>>>> florian.boulay@gmail.com
> >>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>
> >>>>> Hello,
> >>>>>>
> >>>>>> Since 2 days, I am trying to configure Chainsaw v2 for parsing my
> >>>>>> log4j
> >>>>>>
> >>>>> log
> >>>>>
> >>>>>> files, but it always returns "found non matching line...".
> >>>>>>
> >>>>>> Here is my log4j configuration :
> >>>>>> <appender name="crm"
> >>>>>> class="org.apache.log4j.DailyRollingFileAppender">
> >>>>>> ....
> >>>>>> <layout class="org.apache.log4j.PatternLayout">
> >>>>>> <param name="ConversionPattern" value="[%d{dd MMM yyyy
> >>>>>> HH:mm:ss,SSS}] [%p] user: [%x] %c | %m%n"/>
> >>>>>> </layout>
> >>>>>> </appender>
> >>>>>>
> >>>>>> And my Chainsaw configuration :
> >>>>>> <plugin name="logFileReceiver"
> >>>>>> class="org.apache.log4j.varia.LogFilePatternReceiver">
> >>>>>> <param name="fileURL" value="file:///c:/app.log" />
> >>>>>> <param name="timestampFormat" value="dd MMM yyyy
> HH:mm:ss,SSS"/>
> >>>>>> <param name="logFormat" value="[TIMESTAMP] [LEVEL] user: [*] *
> |
> >>>>>> MESSAGE"/>
> >>>>>> <param name="name" value="log app" />
> >>>>>> <param name="tailing" value="true" />
> >>>>>> </plugin>
> >>>>>>
> >>>>>> It does not work. I tried a lot of logFormat, but I do not manage to
> >>>>>> get
> >>>>>>
> >>>>> it
> >>>>>
> >>>>>> work. Can someone help me ?
> >>>>>>
> >>>>>> Thanks
> >>>>>>
> >>>>>>
> >>>>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >>> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >>>
> >>>
> >>
> >
>
Re: problem using Chainsaw, "found non matching line"
Posted by Florian Boulay <fl...@gmail.com>.
When using the format *[TIMESTAMP] **, the updated version of Chainsaw
manages to parse 4 lines of my log file. The old version does not manage to
do it.
However the *** get a lot of lines ! It does not stop when it encounters a
\r\n
2010/7/26 Florian Boulay <fl...@gmail.com>
> Ok I answered to quickly. The updated version still parses my log file, but
> it always display : "found non matching line:..."
>
> 2010/7/26 Florian Boulay <fl...@gmail.com>
>
> Hi,
>>
>> I tried the format [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE with the
>> official version of Chainsaw and the updated version found here :
>> http://people.apache.org/~sdeboy/ <http://people.apache.org/%7Esdeboy/>and It did not work.
>>
>> On the updated version, nothing happen when choosing my chainsaw confg
>> file. No error message in the tab "chainsaw-log". Sound like it did not
>> parse any file. I also tried to delete all files in my .chainsaw directory,
>> but it does not change the behavior of Chainsaw. Maybe I should try with a
>> SocketAppender instead of loading a local file.
>>
>> 2010/7/26 Scott Deboy <sc...@gmail.com>
>>
>> Can you try
>>> [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE
>>>
>>> Also, try the updated version of Chainsaw when you have a chance and see
>>> if that resolves your issue.
>>>
>>> Scott
>>>
>>>
>>>
>>>
>>> On Jul 26, 2010, at 12:25 AM, Florian Boulay <fl...@gmail.com>
>>> wrote:
>>>
>>> Hello,
>>>>
>>>> These two formats do not work :
>>>> - [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
>>>> - [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
>>>>
>>>> I am still searching the right format, I tried just '*' and it still
>>>> does
>>>> not work....
>>>>
>>>> 2010/7/23 Scott Deboy <sc...@gmail.com>
>>>>
>>>> Try:
>>>>> [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
>>>>>
>>>>> Or, if you don't want the user property defined (you probably still
>>>>> want
>>>>> the
>>>>> logger, yes?)
>>>>> [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
>>>>>
>>>>>
>>>>> On Fri, Jul 23, 2010 at 9:15 AM, Florian Boulay <
>>>>> florian.boulay@gmail.com
>>>>>
>>>>>> wrote:
>>>>>>
>>>>>
>>>>> Hello,
>>>>>>
>>>>>> Since 2 days, I am trying to configure Chainsaw v2 for parsing my
>>>>>> log4j
>>>>>>
>>>>> log
>>>>>
>>>>>> files, but it always returns "found non matching line...".
>>>>>>
>>>>>> Here is my log4j configuration :
>>>>>> <appender name="crm"
>>>>>> class="org.apache.log4j.DailyRollingFileAppender">
>>>>>> ....
>>>>>> <layout class="org.apache.log4j.PatternLayout">
>>>>>> <param name="ConversionPattern" value="[%d{dd MMM yyyy
>>>>>> HH:mm:ss,SSS}] [%p] user: [%x] %c | %m%n"/>
>>>>>> </layout>
>>>>>> </appender>
>>>>>>
>>>>>> And my Chainsaw configuration :
>>>>>> <plugin name="logFileReceiver"
>>>>>> class="org.apache.log4j.varia.LogFilePatternReceiver">
>>>>>> <param name="fileURL" value="file:///c:/app.log" />
>>>>>> <param name="timestampFormat" value="dd MMM yyyy HH:mm:ss,SSS"/>
>>>>>> <param name="logFormat" value="[TIMESTAMP] [LEVEL] user: [*] * |
>>>>>> MESSAGE"/>
>>>>>> <param name="name" value="log app" />
>>>>>> <param name="tailing" value="true" />
>>>>>> </plugin>
>>>>>>
>>>>>> It does not work. I tried a lot of logFormat, but I do not manage to
>>>>>> get
>>>>>>
>>>>> it
>>>>>
>>>>>> work. Can someone help me ?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>
>>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>
>>>
>>
>
Re: problem using Chainsaw, "found non matching line"
Posted by Florian Boulay <fl...@gmail.com>.
Ok I answered to quickly. The updated version still parses my log file, but
it always display : "found non matching line:..."
2010/7/26 Florian Boulay <fl...@gmail.com>
> Hi,
>
> I tried the format [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE with the official
> version of Chainsaw and the updated version found here :
> http://people.apache.org/~sdeboy/ <http://people.apache.org/%7Esdeboy/>and It did not work.
>
> On the updated version, nothing happen when choosing my chainsaw confg
> file. No error message in the tab "chainsaw-log". Sound like it did not
> parse any file. I also tried to delete all files in my .chainsaw directory,
> but it does not change the behavior of Chainsaw. Maybe I should try with a
> SocketAppender instead of loading a local file.
>
> 2010/7/26 Scott Deboy <sc...@gmail.com>
>
> Can you try
>> [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE
>>
>> Also, try the updated version of Chainsaw when you have a chance and see
>> if that resolves your issue.
>>
>> Scott
>>
>>
>>
>>
>> On Jul 26, 2010, at 12:25 AM, Florian Boulay <fl...@gmail.com>
>> wrote:
>>
>> Hello,
>>>
>>> These two formats do not work :
>>> - [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
>>> - [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
>>>
>>> I am still searching the right format, I tried just '*' and it still does
>>> not work....
>>>
>>> 2010/7/23 Scott Deboy <sc...@gmail.com>
>>>
>>> Try:
>>>> [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
>>>>
>>>> Or, if you don't want the user property defined (you probably still want
>>>> the
>>>> logger, yes?)
>>>> [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
>>>>
>>>>
>>>> On Fri, Jul 23, 2010 at 9:15 AM, Florian Boulay <
>>>> florian.boulay@gmail.com
>>>>
>>>>> wrote:
>>>>>
>>>>
>>>> Hello,
>>>>>
>>>>> Since 2 days, I am trying to configure Chainsaw v2 for parsing my log4j
>>>>>
>>>> log
>>>>
>>>>> files, but it always returns "found non matching line...".
>>>>>
>>>>> Here is my log4j configuration :
>>>>> <appender name="crm" class="org.apache.log4j.DailyRollingFileAppender">
>>>>> ....
>>>>> <layout class="org.apache.log4j.PatternLayout">
>>>>> <param name="ConversionPattern" value="[%d{dd MMM yyyy
>>>>> HH:mm:ss,SSS}] [%p] user: [%x] %c | %m%n"/>
>>>>> </layout>
>>>>> </appender>
>>>>>
>>>>> And my Chainsaw configuration :
>>>>> <plugin name="logFileReceiver"
>>>>> class="org.apache.log4j.varia.LogFilePatternReceiver">
>>>>> <param name="fileURL" value="file:///c:/app.log" />
>>>>> <param name="timestampFormat" value="dd MMM yyyy HH:mm:ss,SSS"/>
>>>>> <param name="logFormat" value="[TIMESTAMP] [LEVEL] user: [*] * |
>>>>> MESSAGE"/>
>>>>> <param name="name" value="log app" />
>>>>> <param name="tailing" value="true" />
>>>>> </plugin>
>>>>>
>>>>> It does not work. I tried a lot of logFormat, but I do not manage to
>>>>> get
>>>>>
>>>> it
>>>>
>>>>> work. Can someone help me ?
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>>
>
Re: problem using Chainsaw, "found non matching line"
Posted by Florian Boulay <fl...@gmail.com>.
Hi,
I tried the format [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE with the official
version of Chainsaw and the updated version found here :
http://people.apache.org/~sdeboy/ and It did not work.
On the updated version, nothing happen when choosing my chainsaw confg file.
No error message in the tab "chainsaw-log". Sound like it did not parse any
file. I also tried to delete all files in my .chainsaw directory, but it
does not change the behavior of Chainsaw. Maybe I should try with a
SocketAppender instead of loading a local file.
2010/7/26 Scott Deboy <sc...@gmail.com>
> Can you try
> [TIMESTAMP] [LEVEL] * LOGGER | MESSAGE
>
> Also, try the updated version of Chainsaw when you have a chance and see if
> that resolves your issue.
>
> Scott
>
>
>
>
> On Jul 26, 2010, at 12:25 AM, Florian Boulay <fl...@gmail.com>
> wrote:
>
> Hello,
>>
>> These two formats do not work :
>> - [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
>> - [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
>>
>> I am still searching the right format, I tried just '*' and it still does
>> not work....
>>
>> 2010/7/23 Scott Deboy <sc...@gmail.com>
>>
>> Try:
>>> [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
>>>
>>> Or, if you don't want the user property defined (you probably still want
>>> the
>>> logger, yes?)
>>> [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
>>>
>>>
>>> On Fri, Jul 23, 2010 at 9:15 AM, Florian Boulay <
>>> florian.boulay@gmail.com
>>>
>>>> wrote:
>>>>
>>>
>>> Hello,
>>>>
>>>> Since 2 days, I am trying to configure Chainsaw v2 for parsing my log4j
>>>>
>>> log
>>>
>>>> files, but it always returns "found non matching line...".
>>>>
>>>> Here is my log4j configuration :
>>>> <appender name="crm" class="org.apache.log4j.DailyRollingFileAppender">
>>>> ....
>>>> <layout class="org.apache.log4j.PatternLayout">
>>>> <param name="ConversionPattern" value="[%d{dd MMM yyyy
>>>> HH:mm:ss,SSS}] [%p] user: [%x] %c | %m%n"/>
>>>> </layout>
>>>> </appender>
>>>>
>>>> And my Chainsaw configuration :
>>>> <plugin name="logFileReceiver"
>>>> class="org.apache.log4j.varia.LogFilePatternReceiver">
>>>> <param name="fileURL" value="file:///c:/app.log" />
>>>> <param name="timestampFormat" value="dd MMM yyyy HH:mm:ss,SSS"/>
>>>> <param name="logFormat" value="[TIMESTAMP] [LEVEL] user: [*] * |
>>>> MESSAGE"/>
>>>> <param name="name" value="log app" />
>>>> <param name="tailing" value="true" />
>>>> </plugin>
>>>>
>>>> It does not work. I tried a lot of logFormat, but I do not manage to get
>>>>
>>> it
>>>
>>>> work. Can someone help me ?
>>>>
>>>> Thanks
>>>>
>>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
Re: problem using Chainsaw, "found non matching line"
Posted by Scott Deboy <sc...@gmail.com>.
Can you try
[TIMESTAMP] [LEVEL] * LOGGER | MESSAGE
Also, try the updated version of Chainsaw when you have a chance and
see if that resolves your issue.
Scott
On Jul 26, 2010, at 12:25 AM, Florian Boulay
<fl...@gmail.com> wrote:
> Hello,
>
> These two formats do not work :
> - [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
> - [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
>
> I am still searching the right format, I tried just '*' and it still
> does
> not work....
>
> 2010/7/23 Scott Deboy <sc...@gmail.com>
>
>> Try:
>> [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
>>
>> Or, if you don't want the user property defined (you probably still
>> want
>> the
>> logger, yes?)
>> [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
>>
>>
>> On Fri, Jul 23, 2010 at 9:15 AM, Florian Boulay <florian.boulay@gmail.com
>>> wrote:
>>
>>> Hello,
>>>
>>> Since 2 days, I am trying to configure Chainsaw v2 for parsing my
>>> log4j
>> log
>>> files, but it always returns "found non matching line...".
>>>
>>> Here is my log4j configuration :
>>> <appender name="crm"
>>> class="org.apache.log4j.DailyRollingFileAppender">
>>> ....
>>> <layout class="org.apache.log4j.PatternLayout">
>>> <param name="ConversionPattern" value="[%d{dd MMM yyyy
>>> HH:mm:ss,SSS}] [%p] user: [%x] %c | %m%n"/>
>>> </layout>
>>> </appender>
>>>
>>> And my Chainsaw configuration :
>>> <plugin name="logFileReceiver"
>>> class="org.apache.log4j.varia.LogFilePatternReceiver">
>>> <param name="fileURL" value="file:///c:/app.log" />
>>> <param name="timestampFormat" value="dd MMM yyyy
>>> HH:mm:ss,SSS"/>
>>> <param name="logFormat" value="[TIMESTAMP] [LEVEL] user: [*]
>>> * |
>>> MESSAGE"/>
>>> <param name="name" value="log app" />
>>> <param name="tailing" value="true" />
>>> </plugin>
>>>
>>> It does not work. I tried a lot of logFormat, but I do not manage
>>> to get
>> it
>>> work. Can someone help me ?
>>>
>>> Thanks
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: problem using Chainsaw, "found non matching line"
Posted by Florian Boulay <fl...@gmail.com>.
Hello,
These two formats do not work :
- [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
- [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
I am still searching the right format, I tried just '*' and it still does
not work....
2010/7/23 Scott Deboy <sc...@gmail.com>
> Try:
> [TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
>
> Or, if you don't want the user property defined (you probably still want
> the
> logger, yes?)
> [TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
>
>
> On Fri, Jul 23, 2010 at 9:15 AM, Florian Boulay <florian.boulay@gmail.com
> >wrote:
>
> > Hello,
> >
> > Since 2 days, I am trying to configure Chainsaw v2 for parsing my log4j
> log
> > files, but it always returns "found non matching line...".
> >
> > Here is my log4j configuration :
> > <appender name="crm" class="org.apache.log4j.DailyRollingFileAppender">
> > ....
> > <layout class="org.apache.log4j.PatternLayout">
> > <param name="ConversionPattern" value="[%d{dd MMM yyyy
> > HH:mm:ss,SSS}] [%p] user: [%x] %c | %m%n"/>
> > </layout>
> > </appender>
> >
> > And my Chainsaw configuration :
> > <plugin name="logFileReceiver"
> > class="org.apache.log4j.varia.LogFilePatternReceiver">
> > <param name="fileURL" value="file:///c:/app.log" />
> > <param name="timestampFormat" value="dd MMM yyyy HH:mm:ss,SSS"/>
> > <param name="logFormat" value="[TIMESTAMP] [LEVEL] user: [*] * |
> > MESSAGE"/>
> > <param name="name" value="log app" />
> > <param name="tailing" value="true" />
> > </plugin>
> >
> > It does not work. I tried a lot of logFormat, but I do not manage to get
> it
> > work. Can someone help me ?
> >
> > Thanks
> >
>
Re: problem using Chainsaw, "found non matching line"
Posted by Scott Deboy <sc...@gmail.com>.
Try:
[TIMESTAMP] [LEVEL] user:[PROP(USER)] LOGGER | MESSAGE
Or, if you don't want the user property defined (you probably still want the
logger, yes?)
[TIMESTAMP] [LEVEL] user:[*] LOGGER | MESSAGE
On Fri, Jul 23, 2010 at 9:15 AM, Florian Boulay <fl...@gmail.com>wrote:
> Hello,
>
> Since 2 days, I am trying to configure Chainsaw v2 for parsing my log4j log
> files, but it always returns "found non matching line...".
>
> Here is my log4j configuration :
> <appender name="crm" class="org.apache.log4j.DailyRollingFileAppender">
> ....
> <layout class="org.apache.log4j.PatternLayout">
> <param name="ConversionPattern" value="[%d{dd MMM yyyy
> HH:mm:ss,SSS}] [%p] user: [%x] %c | %m%n"/>
> </layout>
> </appender>
>
> And my Chainsaw configuration :
> <plugin name="logFileReceiver"
> class="org.apache.log4j.varia.LogFilePatternReceiver">
> <param name="fileURL" value="file:///c:/app.log" />
> <param name="timestampFormat" value="dd MMM yyyy HH:mm:ss,SSS"/>
> <param name="logFormat" value="[TIMESTAMP] [LEVEL] user: [*] * |
> MESSAGE"/>
> <param name="name" value="log app" />
> <param name="tailing" value="true" />
> </plugin>
>
> It does not work. I tried a lot of logFormat, but I do not manage to get it
> work. Can someone help me ?
>
> Thanks
>