I see following WARNINGS
log4j:WARN Continuable parsing error 19 and column 97
log4j:WARN Element type "rewritePolicy" must be declared.
log4j:WARN Continuable parsing error 22 and column 12
log4j:WARN The content of element type "appender" must match
"(errorHandler?,param*,rollingPolicy?,triggeringPolicy?,connectionSource
?,layout?,filter*,appender-ref*)".
Following is config
<appender name="rewrite"
class="org.apache.log4j.rewrite.RewriteAppender">
<appender name="socket" class="org.apache.log4j.net.SocketAppender">
<param name="Port" value="12346"/>
<param name="RemoteHost" value="localhost"/>
<param name="Application" value="app1"/>
<param name="ReconnectionDelay" value="60000"/>
<param name="Threshold" value="ALL"/>
</appender>
<rewritePolicy name="propertyPolicy"
class="org.apache.log4j.rewrite.PropertyRewritePolicy"> ////This is line
number 19
<param name="properties" value="logFile=server2.log"/>
</rewritePolicy>
</appender>////This is line number 22
I included following jars( which in chainsaw) in my classpath
1.extras
2. receivers
3.components
Thanks a Lot
VGSS
-----Original Message-----
From: Scott Deboy [mailto:[email protected]]
Sent: Thursday, September 15, 2011 12:30 PM
To: Log4J Users List
Subject: Re: log4j----Edit the event received
Chainsaw includes those jars in its standalone zip.
The extras companion has been released:
http://logging.apache.org/log4j/companions/extras/download.html
The receivers and component companions have not yet been officially
released, so you would have to build them from source if you didn't use
the
jars from the chainsaw zip.
http://logging.apache.org/log4j/companions/component/index.html
http://logging.apache.org/log4j/companions/receivers/index.html
Scott
On Wed, Sep 14, 2011 at 7:25 PM, Konduru, Geetha
<[email protected]>wrote:
> Where can I download the receivers companion jar, component companion
> jar and extra companion jar.
>
> Thank U,
> VGSS
>
>
> -----Original Message-----
> From: Scott Deboy [mailto:[email protected]]
> Sent: Wednesday, September 14, 2011 4:50 PM
> To: Log4J Users List
> Subject: Re: log4j----Edit the event received
>
> There are only three unique attributes provided for socket-received
> events:
> hostname
> remoteSourceInfo
> application (if set on appender)
>
> If you can't leverage application and would like to use additional
> properties to identify instances, there is a mechanism that supports
> that
> (via configuration): RewriteAppender
>
> RewriteAppender allows you to modify event attributes (or add
> properties)
> before sending the event to the appender.
>
> A RewriteAppender expects a nested appender (your SocketAppender) and
a
> RewritePolicy.
>
> You can use a PropertyRewritePolicy as a quick way to add custom
> properties
> to each event.
>
> This requires you to add the receivers companion jar and probably
> component
> companion jar (not sure about extras companion) to your appender side.
>
>
http://logging.apache.org/log4j/companions/receivers/apidocs/org/apache/
> log4j/rewrite/RewriteAppender.html
>
http://logging.apache.org/log4j/companions/receivers/apidocs/org/apache/
> log4j/rewrite/RewritePolicy.html
>
> Example configuration (didn't run this, but it should be correct) that
> will
> add two properties to each event, somepropertyname1 and
> somepropertyname2.
>
> <appender name="rewrite"
> class="org.apache.log4j.rewrite.RewriteAppender">
> <appender name="socket"
class="org.apache.log4j.net.SocketAppender">
> <param name="Port" value="12346"/>
> <param name="RemoteHost" value="localhost"/>
> <param name="Application" value="app1"/>
> <param name="ReconnectionDelay" value="60000"/>
> <param name="Threshold" value="ALL"/>
> </appender>
> <RewritePolicy name="propertyPolicy"
> class="org.apache.log4j.rewrite.PropertyRewritePolicy">
> <param name="properties"
>
value="somepropertyname1=somepropertyvalue1,somepropertyname2=someproper
> tyvalue2">
> </RewritePolicy>
> </appender>
>
> Scott
>
>
> On Wed, Sep 14, 2011 at 1:29 PM, Konduru, Geetha
> <[email protected]>wrote:
>
> > Actually issue is , We have 100 server instances running on 20
> > different machines (5 instances per machine).
> >
> > We want to merge and see them,
> >
> > When I merge , seeing " log4j.remoteSourceInfo" I can say
particular
> > logging event is generated by server instances running on one
> particular
> > machine, Is there a way to figure out which particular Instance out
of
> 5
> > instances running on that particular machine.
> >
> > Thank u,
> > VGSS
> >
> > -----Original Message-----
> > From: Scott Deboy [mailto:[email protected]]
> > Sent: Wednesday, September 14, 2011 4:15 PM
> > To: Log4J Users List
> > Subject: Re: log4j----Edit the event received
> >
> > The SocketReceiver adds two properties to each event:
> > hostname
> > log4j.remoteSourceInfo
> >
> > With the developer snapshot of Chainsaw you should see those as
> > individual
> > columns in the table. If they aren't displayed by default you can
> > enable
> > them via the tab preferences menu (select Columns).
> >
> > Scott
> >
> > On Wed, Sep 14, 2011 at 12:38 PM, Konduru, Geetha
> > <[email protected]>wrote:
> >
> > > Hi,
> > >
> > >
> > >
> > > What I am looking for is, every event received by SocketAppender,
> > even
> > > before it send to remote machine, it must append to the event(on
> > which
> > > log4j is running).
> > >
> > >
> > >
> > > Can any one please tell me a solution for this.
> > >
> > >
> > >
> > > Example: if application(running on machine HOSTNAME) logs message
"I
> > am
> > > a Logging event", than SOCKET APPENDER must send following to
REMOTE
> > > machine(or SOCKET RECEIVER on Remote machine should receive
> following
> > as
> > > log message).
> > >
> > >
> > >
> > > "HOSTNAME:I am a Logging event"
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Thank U,
> > >
> > > VGSS
> > >
> > >
> **********************************************************************
> > > This e-mail message and any attachments contain confidential
> > information
> > > from Medco. If you are not the intended recipient, you are hereby
> > notified
> > > that disclosure, printing, copying, distribution, or the taking of
> any
> > > action in reliance on the contents of this electronic information
is
> > > strictly prohibited. If you have received this e-mail message in
> > error,
> > > please immediately notify the sender by reply message and then
> delete
> > the
> > > electronic message and any attachments.
> > >
> >
> >
**********************************************************************
> > This e-mail message and any attachments contain confidential
> information
> > from Medco. If you are not the intended recipient, you are hereby
> notified
> > that disclosure, printing, copying, distribution, or the taking of
any
> > action in reliance on the contents of this electronic information is
> > strictly prohibited. If you have received this e-mail message in
> error,
> > please immediately notify the sender by reply message and then
delete
> the
> > electronic message and any attachments.
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
> **********************************************************************
> This e-mail message and any attachments contain confidential
information
> from Medco. If you are not the intended recipient, you are hereby
notified
> that disclosure, printing, copying, distribution, or the taking of any
> action in reliance on the contents of this electronic information is
> strictly prohibited. If you have received this e-mail message in
error,
> please immediately notify the sender by reply message and then delete
the
> electronic message and any attachments.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
**********************************************************************
This e-mail message and any attachments contain confidential information from
Medco. If you are not the intended recipient, you are hereby notified that
disclosure, printing, copying, distribution, or the taking of any action in
reliance on the contents of this electronic information is strictly prohibited.
If you have received this e-mail message in error, please immediately notify
the sender by reply message and then delete the electronic message and any
attachments.
