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 Evan J <ma...@gmail.com> on 2014/05/01 02:21:22 UTC
Web Service Appender
I searched around, but I could not find an off-the-shelf Appender that
sends logs to a web service. Is there any?
RE: Web Service Appender
Posted by Wa...@DellTeam.com.
Dell - Internal Use - Confidential
Try this url
http://www.ibm.com/developerworks/library/ws-log4j/index.html
-----Original Message-----
From: Evan J [mailto:maps.this.address@gmail.com]
Sent: Wednesday, April 30, 2014 7:21 PM
To: log4j-user@logging.apache.org
Subject: Web Service Appender
I searched around, but I could not find an off-the-shelf Appender that sends logs to a web service. Is there any?
RE: Web Service Appender
Posted by Wa...@DellTeam.com.
Dell - Internal Use - Confidential
Marshalling and unmarshalling is indeed inefficient, being CPU intensive, which competes for cycles with the main processes. JMS appears to have internal queuing, persistence to disk, and
Asynchronous transport acknowledgements. It would be good to relieve the CPU pressure by using parallel processing in the stream, perhaps tux.
-----Original Message-----
From: Evan J [mailto:maps.this.address@gmail.com]
Sent: Thursday, May 01, 2014 12:54 PM
To: Log4J Users List
Subject: Re: Web Service Appender
This is just gone off the tangent line... in a good way though.
We are going to try to push back and redesign the process to just simply make use of JMSAppender to put messages on a queue and have JMS clients consume them (and ultimately insert the logs into a database -- maybe use JSON for messages). The MQ runs within an integration broker, hence an initial idea of routing logging SOAP/service calls through the same broker that handles/routes other web services.
This whole marshalling and unmarshalling is very inefficient, on top of a fact that this proposed logging service is entirely internal to begin with.
On Thu, May 1, 2014 at 10:59 AM, Ralph Goers wrote:
> This thread originally started to ask about logging to a web service
> (that term usually implies SOAP). It seems to have gone off into
> another direction and I'm not sure if there is still a question here
> someone wants answered. If you are making a proposal for an
> enhancement to Log4j 2 I am not sure what it is.
>
> Ralph
>
> On May 1, 2014, at 8:51 AM,
> wrote:
>
> > Dell - Internal Use - Confidential
> > I take it we were discussing the possibilities for high speed
> > production
> logging. Previous people have rightly pointed out that a simplistic
> approach using soap might be ineffecient
> >
> > -----Original Message-----
> > From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> > Sent: Thursday, May 01, 2014 10:36 AM
> > To: Log4J Users List
> > Subject: Re: Web Service Appender
> >
> > Thats fine. I'm just not really sure what the question is any more.
> >
> > Ralph
> >
> > On May 1, 2014, at 8:22 AM, Walter_Marvin@DellTeam.com wrote:
> >
> >> Dell - Internal Use - Confidential
> >> As I say there are a lot of architectural options. We need to
> >> decide on
> one. Having th ability to modify log4j should make whatever
> architecture is chosen cleaner.
> >>
> >> Thanks
> >>
> >> Walter
> >>
> >> -----Original Message-----
> >> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> >> Sent: Thursday, May 01, 2014 10:16 AM
> >> To: Log4J Users List
> >> Subject: Re: Web Service Appender
> >>
> >> What you are describing is why I added the integration to Flume. It
> >> is
> very, very good at collecting log events and forwarding them. However,
> you could use a JMS appender to write your events to the MQ queue.
> >>
> >> Ralph
> >>
> >> On May 1, 2014, at 7:15 AM, Evan J wrote:
> >>
> >>> Hi Ralph,
> >>>
> >>> All the request and response messages, some header data, with
> >>> additional information, are placed in an MDC, packaged in an
> >>> Appender and sent to an MQ queue which, ultimately, makes a call
> >>> to the service. It's a centralized logging model for all the
> >>> applications in a cluster. Frankly, I don't like the design nor
> >>> the setup, but I don't
> make such decisions (or requirements).
> >>>
> >>>
> >>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
> >>>
> >>>> A web service to do what? Logging via SOAP would be extremely
> >>>> slow if every log event is a single request. Can you elaborate on
> >>>> what you really want to do?
> >>>>
> >>>> Ralph
> >>>>
> >>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
> >>>>
> >>>>> Thanks for verifying this. I thought I might be missing an
> >>>>> obvious, and this has already been implemented by at least someone.
> >>>>>
> >>>>>
> >>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
> >>>> wrote:
> >>>>>
> >>>>>> Evan, no I'm not aware of any appender that logs to a web service.
> >>>>>>
> >>>>>>
> >>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
> >>>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> I searched around, but I could not find an off-the-shelf
> >>>>>>> Appender that sends logs to a web service. Is there any?
> >>>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>> -----------------------------------------------------------------
> >>>> ---
> >>>> - To unsubscribe, e-mail:
> >>>> log4j-user-unsubscribe@logging.apache.org
> >>>> For additional commands, e-mail:
> >>>> log4j-user-help@logging.apache.org
> >>>>
> >>>>
> >>
> >>
> >> -------------------------------------------------------------------
> >> -- To unsubscribe, e-mail:
> >> log4j-user-unsubscribe@logging.apache.org
> >> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
Re: Web Service Appender
Posted by Matt Sicker <bo...@gmail.com>.
Wow I can't type good. Thanks.
On 1 May 2014 21:42, Ralph Goers <rg...@apache.org> wrote:
> Flume, not Felix.
>
> Sent from my iPad
>
> > On May 1, 2014, at 1:28 PM, Matt Sicker <bo...@gmail.com> wrote:
> >
> > Your best bets for this are certainly Felix, JMS, or maybe even Syslog
> (the
> > new RFC version) if you've got a server set up for that already. I'm
> going
> > to back up Ralph's idea here that Felix really is the best way to go for
> > this situation. It's one of the primary use cases for Felix (e.g., in
> EC2,
> > it's great for centralized logging).
> >
> >
> >> On 1 May 2014 12:54, Evan J <ma...@gmail.com> wrote:
> >>
> >> This is just gone off the tangent line... in a good way though.
> >>
> >> We are going to try to push back and redesign the process to just simply
> >> make use of JMSAppender to put messages on a queue and have JMS clients
> >> consume them (and ultimately insert the logs into a database -- maybe
> use
> >> JSON for messages). The MQ runs within an integration broker, hence an
> >> initial idea of routing logging SOAP/service calls through the same
> broker
> >> that handles/routes other web services.
> >>
> >> This whole marshalling and unmarshalling is very inefficient, on top of
> a
> >> fact that this proposed logging service is entirely internal to begin
> with.
> >>
> >>
> >> On Thu, May 1, 2014 at 10:59 AM, Ralph Goers <
> ralph.goers@dslextreme.com
> >>> wrote:
> >>
> >>> This thread originally started to ask about logging to a web service
> >> (that
> >>> term usually implies SOAP). It seems to have gone off into another
> >>> direction and I’m not sure if there is still a question here someone
> >> wants
> >>> answered. If you are making a proposal for an enhancement to Log4j 2 I
> >> am
> >>> not sure what it is.
> >>>
> >>> Ralph
> >>>
> >>> On May 1, 2014, at 8:51 AM, <Wa...@DellTeam.com>
> >>> <Wa...@DellTeam.com> wrote:
> >>>
> >>>> Dell - Internal Use - Confidential
> >>>> I take it we were discussing the possibilities for high speed
> >> production
> >>> logging. Previous people have rightly pointed out that a simplistic
> >>> approach using soap might be ineffecient
> >>>>
> >>>> -----Original Message-----
> >>>> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> >>>> Sent: Thursday, May 01, 2014 10:36 AM
> >>>> To: Log4J Users List
> >>>> Subject: Re: Web Service Appender
> >>>>
> >>>> Thats fine. I'm just not really sure what the question is any more.
> >>>>
> >>>> Ralph
> >>>>
> >>>>> On May 1, 2014, at 8:22 AM, Walter_Marvin@DellTeam.com wrote:
> >>>>>
> >>>>> Dell - Internal Use - Confidential
> >>>>> As I say there are a lot of architectural options. We need to decide
> >> on
> >>> one. Having th ability to modify log4j should make whatever
> architecture
> >> is
> >>> chosen cleaner.
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>> Walter
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> >>>>> Sent: Thursday, May 01, 2014 10:16 AM
> >>>>> To: Log4J Users List
> >>>>> Subject: Re: Web Service Appender
> >>>>>
> >>>>> What you are describing is why I added the integration to Flume. It
> is
> >>> very, very good at collecting log events and forwarding them. However,
> >> you
> >>> could use a JMS appender to write your events to the MQ queue.
> >>>>>
> >>>>> Ralph
> >>>>>
> >>>>>> On May 1, 2014, at 7:15 AM, Evan J wrote:
> >>>>>>
> >>>>>> Hi Ralph,
> >>>>>>
> >>>>>> All the request and response messages, some header data, with
> >>>>>> additional information, are placed in an MDC, packaged in an
> Appender
> >>>>>> and sent to an MQ queue which, ultimately, makes a call to the
> >>>>>> service. It's a centralized logging model for all the applications
> in
> >>>>>> a cluster. Frankly, I don't like the design nor the setup, but I
> >> don't
> >>> make such decisions (or requirements).
> >>>>>>
> >>>>>>
> >>>>>>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
> >>>>>>>
> >>>>>>> A web service to do what? Logging via SOAP would be extremely slow
> >>>>>>> if every log event is a single request. Can you elaborate on what
> >>>>>>> you really want to do?
> >>>>>>>
> >>>>>>> Ralph
> >>>>>>>
> >>>>>>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
> >>>>>>>>
> >>>>>>>> Thanks for verifying this. I thought I might be missing an
> obvious,
> >>>>>>>> and this has already been implemented by at least someone.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Evan, no I'm not aware of any appender that logs to a web
> service.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
> >>>>>>>>>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> I searched around, but I could not find an off-the-shelf
> Appender
> >>>>>>>>>> that sends logs to a web service. Is there any?
> >>>>>>>
> >>>>>>>
> >>>>>>>
> --------------------------------------------------------------------
> >>>>>>> - To unsubscribe, e-mail:
> log4j-user-unsubscribe@logging.apache.org
> >>>>>>> For additional commands, e-mail:
> log4j-user-help@logging.apache.org
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >>>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >>> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
--
Matt Sicker <bo...@gmail.com>
Re: Web Service Appender
Posted by Ralph Goers <rg...@apache.org>.
Flume, not Felix.
Sent from my iPad
> On May 1, 2014, at 1:28 PM, Matt Sicker <bo...@gmail.com> wrote:
>
> Your best bets for this are certainly Felix, JMS, or maybe even Syslog (the
> new RFC version) if you've got a server set up for that already. I'm going
> to back up Ralph's idea here that Felix really is the best way to go for
> this situation. It's one of the primary use cases for Felix (e.g., in EC2,
> it's great for centralized logging).
>
>
>> On 1 May 2014 12:54, Evan J <ma...@gmail.com> wrote:
>>
>> This is just gone off the tangent line... in a good way though.
>>
>> We are going to try to push back and redesign the process to just simply
>> make use of JMSAppender to put messages on a queue and have JMS clients
>> consume them (and ultimately insert the logs into a database -- maybe use
>> JSON for messages). The MQ runs within an integration broker, hence an
>> initial idea of routing logging SOAP/service calls through the same broker
>> that handles/routes other web services.
>>
>> This whole marshalling and unmarshalling is very inefficient, on top of a
>> fact that this proposed logging service is entirely internal to begin with.
>>
>>
>> On Thu, May 1, 2014 at 10:59 AM, Ralph Goers <ralph.goers@dslextreme.com
>>> wrote:
>>
>>> This thread originally started to ask about logging to a web service
>> (that
>>> term usually implies SOAP). It seems to have gone off into another
>>> direction and I’m not sure if there is still a question here someone
>> wants
>>> answered. If you are making a proposal for an enhancement to Log4j 2 I
>> am
>>> not sure what it is.
>>>
>>> Ralph
>>>
>>> On May 1, 2014, at 8:51 AM, <Wa...@DellTeam.com>
>>> <Wa...@DellTeam.com> wrote:
>>>
>>>> Dell - Internal Use - Confidential
>>>> I take it we were discussing the possibilities for high speed
>> production
>>> logging. Previous people have rightly pointed out that a simplistic
>>> approach using soap might be ineffecient
>>>>
>>>> -----Original Message-----
>>>> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
>>>> Sent: Thursday, May 01, 2014 10:36 AM
>>>> To: Log4J Users List
>>>> Subject: Re: Web Service Appender
>>>>
>>>> Thats fine. I'm just not really sure what the question is any more.
>>>>
>>>> Ralph
>>>>
>>>>> On May 1, 2014, at 8:22 AM, Walter_Marvin@DellTeam.com wrote:
>>>>>
>>>>> Dell - Internal Use - Confidential
>>>>> As I say there are a lot of architectural options. We need to decide
>> on
>>> one. Having th ability to modify log4j should make whatever architecture
>> is
>>> chosen cleaner.
>>>>>
>>>>> Thanks
>>>>>
>>>>> Walter
>>>>>
>>>>> -----Original Message-----
>>>>> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
>>>>> Sent: Thursday, May 01, 2014 10:16 AM
>>>>> To: Log4J Users List
>>>>> Subject: Re: Web Service Appender
>>>>>
>>>>> What you are describing is why I added the integration to Flume. It is
>>> very, very good at collecting log events and forwarding them. However,
>> you
>>> could use a JMS appender to write your events to the MQ queue.
>>>>>
>>>>> Ralph
>>>>>
>>>>>> On May 1, 2014, at 7:15 AM, Evan J wrote:
>>>>>>
>>>>>> Hi Ralph,
>>>>>>
>>>>>> All the request and response messages, some header data, with
>>>>>> additional information, are placed in an MDC, packaged in an Appender
>>>>>> and sent to an MQ queue which, ultimately, makes a call to the
>>>>>> service. It's a centralized logging model for all the applications in
>>>>>> a cluster. Frankly, I don't like the design nor the setup, but I
>> don't
>>> make such decisions (or requirements).
>>>>>>
>>>>>>
>>>>>>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
>>>>>>>
>>>>>>> A web service to do what? Logging via SOAP would be extremely slow
>>>>>>> if every log event is a single request. Can you elaborate on what
>>>>>>> you really want to do?
>>>>>>>
>>>>>>> Ralph
>>>>>>>
>>>>>>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
>>>>>>>>
>>>>>>>> Thanks for verifying this. I thought I might be missing an obvious,
>>>>>>>> and this has already been implemented by at least someone.
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Evan, no I'm not aware of any appender that logs to a web service.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
>>>>>>>>>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I searched around, but I could not find an off-the-shelf Appender
>>>>>>>>>> that sends logs to a web service. Is there any?
>>>>>>>
>>>>>>>
>>>>>>> --------------------------------------------------------------------
>>>>>>> - To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>>>>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Web Service Appender
Posted by Matt Sicker <bo...@gmail.com>.
Your best bets for this are certainly Felix, JMS, or maybe even Syslog (the
new RFC version) if you've got a server set up for that already. I'm going
to back up Ralph's idea here that Felix really is the best way to go for
this situation. It's one of the primary use cases for Felix (e.g., in EC2,
it's great for centralized logging).
On 1 May 2014 12:54, Evan J <ma...@gmail.com> wrote:
> This is just gone off the tangent line... in a good way though.
>
> We are going to try to push back and redesign the process to just simply
> make use of JMSAppender to put messages on a queue and have JMS clients
> consume them (and ultimately insert the logs into a database -- maybe use
> JSON for messages). The MQ runs within an integration broker, hence an
> initial idea of routing logging SOAP/service calls through the same broker
> that handles/routes other web services.
>
> This whole marshalling and unmarshalling is very inefficient, on top of a
> fact that this proposed logging service is entirely internal to begin with.
>
>
> On Thu, May 1, 2014 at 10:59 AM, Ralph Goers <ralph.goers@dslextreme.com
> >wrote:
>
> > This thread originally started to ask about logging to a web service
> (that
> > term usually implies SOAP). It seems to have gone off into another
> > direction and I’m not sure if there is still a question here someone
> wants
> > answered. If you are making a proposal for an enhancement to Log4j 2 I
> am
> > not sure what it is.
> >
> > Ralph
> >
> > On May 1, 2014, at 8:51 AM, <Wa...@DellTeam.com>
> > <Wa...@DellTeam.com> wrote:
> >
> > > Dell - Internal Use - Confidential
> > > I take it we were discussing the possibilities for high speed
> production
> > logging. Previous people have rightly pointed out that a simplistic
> > approach using soap might be ineffecient
> > >
> > > -----Original Message-----
> > > From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> > > Sent: Thursday, May 01, 2014 10:36 AM
> > > To: Log4J Users List
> > > Subject: Re: Web Service Appender
> > >
> > > Thats fine. I'm just not really sure what the question is any more.
> > >
> > > Ralph
> > >
> > > On May 1, 2014, at 8:22 AM, Walter_Marvin@DellTeam.com wrote:
> > >
> > >> Dell - Internal Use - Confidential
> > >> As I say there are a lot of architectural options. We need to decide
> on
> > one. Having th ability to modify log4j should make whatever architecture
> is
> > chosen cleaner.
> > >>
> > >> Thanks
> > >>
> > >> Walter
> > >>
> > >> -----Original Message-----
> > >> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> > >> Sent: Thursday, May 01, 2014 10:16 AM
> > >> To: Log4J Users List
> > >> Subject: Re: Web Service Appender
> > >>
> > >> What you are describing is why I added the integration to Flume. It is
> > very, very good at collecting log events and forwarding them. However,
> you
> > could use a JMS appender to write your events to the MQ queue.
> > >>
> > >> Ralph
> > >>
> > >> On May 1, 2014, at 7:15 AM, Evan J wrote:
> > >>
> > >>> Hi Ralph,
> > >>>
> > >>> All the request and response messages, some header data, with
> > >>> additional information, are placed in an MDC, packaged in an Appender
> > >>> and sent to an MQ queue which, ultimately, makes a call to the
> > >>> service. It's a centralized logging model for all the applications in
> > >>> a cluster. Frankly, I don't like the design nor the setup, but I
> don't
> > make such decisions (or requirements).
> > >>>
> > >>>
> > >>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
> > >>>
> > >>>> A web service to do what? Logging via SOAP would be extremely slow
> > >>>> if every log event is a single request. Can you elaborate on what
> > >>>> you really want to do?
> > >>>>
> > >>>> Ralph
> > >>>>
> > >>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
> > >>>>
> > >>>>> Thanks for verifying this. I thought I might be missing an obvious,
> > >>>>> and this has already been implemented by at least someone.
> > >>>>>
> > >>>>>
> > >>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
> > >>>> wrote:
> > >>>>>
> > >>>>>> Evan, no I'm not aware of any appender that logs to a web service.
> > >>>>>>
> > >>>>>>
> > >>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
> > >>>>>>
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>>> I searched around, but I could not find an off-the-shelf Appender
> > >>>>>>> that sends logs to a web service. Is there any?
> > >>>>>>>
> > >>>>>>
> > >>>>
> > >>>>
> > >>>> --------------------------------------------------------------------
> > >>>> - To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > >>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
> > >>>>
> > >>>>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > >> For additional commands, e-mail: log4j-user-help@logging.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > > For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
>
--
Matt Sicker <bo...@gmail.com>
Re: Web Service Appender
Posted by Evan J <ma...@gmail.com>.
This is just gone off the tangent line... in a good way though.
We are going to try to push back and redesign the process to just simply
make use of JMSAppender to put messages on a queue and have JMS clients
consume them (and ultimately insert the logs into a database -- maybe use
JSON for messages). The MQ runs within an integration broker, hence an
initial idea of routing logging SOAP/service calls through the same broker
that handles/routes other web services.
This whole marshalling and unmarshalling is very inefficient, on top of a
fact that this proposed logging service is entirely internal to begin with.
On Thu, May 1, 2014 at 10:59 AM, Ralph Goers <ra...@dslextreme.com>wrote:
> This thread originally started to ask about logging to a web service (that
> term usually implies SOAP). It seems to have gone off into another
> direction and I’m not sure if there is still a question here someone wants
> answered. If you are making a proposal for an enhancement to Log4j 2 I am
> not sure what it is.
>
> Ralph
>
> On May 1, 2014, at 8:51 AM, <Wa...@DellTeam.com>
> <Wa...@DellTeam.com> wrote:
>
> > Dell - Internal Use - Confidential
> > I take it we were discussing the possibilities for high speed production
> logging. Previous people have rightly pointed out that a simplistic
> approach using soap might be ineffecient
> >
> > -----Original Message-----
> > From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> > Sent: Thursday, May 01, 2014 10:36 AM
> > To: Log4J Users List
> > Subject: Re: Web Service Appender
> >
> > Thats fine. I'm just not really sure what the question is any more.
> >
> > Ralph
> >
> > On May 1, 2014, at 8:22 AM, Walter_Marvin@DellTeam.com wrote:
> >
> >> Dell - Internal Use - Confidential
> >> As I say there are a lot of architectural options. We need to decide on
> one. Having th ability to modify log4j should make whatever architecture is
> chosen cleaner.
> >>
> >> Thanks
> >>
> >> Walter
> >>
> >> -----Original Message-----
> >> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> >> Sent: Thursday, May 01, 2014 10:16 AM
> >> To: Log4J Users List
> >> Subject: Re: Web Service Appender
> >>
> >> What you are describing is why I added the integration to Flume. It is
> very, very good at collecting log events and forwarding them. However, you
> could use a JMS appender to write your events to the MQ queue.
> >>
> >> Ralph
> >>
> >> On May 1, 2014, at 7:15 AM, Evan J wrote:
> >>
> >>> Hi Ralph,
> >>>
> >>> All the request and response messages, some header data, with
> >>> additional information, are placed in an MDC, packaged in an Appender
> >>> and sent to an MQ queue which, ultimately, makes a call to the
> >>> service. It's a centralized logging model for all the applications in
> >>> a cluster. Frankly, I don't like the design nor the setup, but I don't
> make such decisions (or requirements).
> >>>
> >>>
> >>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
> >>>
> >>>> A web service to do what? Logging via SOAP would be extremely slow
> >>>> if every log event is a single request. Can you elaborate on what
> >>>> you really want to do?
> >>>>
> >>>> Ralph
> >>>>
> >>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
> >>>>
> >>>>> Thanks for verifying this. I thought I might be missing an obvious,
> >>>>> and this has already been implemented by at least someone.
> >>>>>
> >>>>>
> >>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
> >>>> wrote:
> >>>>>
> >>>>>> Evan, no I'm not aware of any appender that logs to a web service.
> >>>>>>
> >>>>>>
> >>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
> >>>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> I searched around, but I could not find an off-the-shelf Appender
> >>>>>>> that sends logs to a web service. Is there any?
> >>>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>> --------------------------------------------------------------------
> >>>> - To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >>>>
> >>>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
Re: Web Service Appender
Posted by Evan J <ma...@gmail.com>.
This implementation is old and uses JAX-RPC/RMI calls which usually comes
up on top of search results for web service appenders. But thanks anyway.
On Mon, May 5, 2014 at 8:48 AM, <Wa...@dellteam.com> wrote:
> Dell - Internal Use - Confidential
> http://www.ibm.com/developerworks/library/ws-log4j/index.html
>
> -----Original Message-----
> From: Evan J [mailto:maps.this.address@gmail.com]
> Sent: Monday, May 05, 2014 8:29 AM
> To: Log4J Users List
> Subject: Re: Web Service Appender
>
> Hi Walter,
>
> Can you point me to where one can try these freeware web service appenders?
> Thanks.
>
>
> On Mon, May 5, 2014 at 8:23 AM, wrote:
>
> > Dell - Internal Use - Confidential
> > I just saying we have the ability to work with log4j directly at this
> > point. That should be useful since a custom appender will probably be
> > needed for speed reasons, There are appenders for web services already
> > written and available as freeware
> >
> > Thanks
> >
> > Walter
> >
> > -----Original Message-----
> > From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> > Sent: Thursday, May 01, 2014 10:59 AM
> > To: Log4J Users List
> > Subject: Re: Web Service Appender
> >
> > This thread originally started to ask about logging to a web service
> > (that term usually implies SOAP). It seems to have gone off into
> > another direction and I'm not sure if there is still a question here
> > someone wants answered. If you are making a proposal for an
> > enhancement to Log4j 2 I am not sure what it is.
> >
> > Ralph
> >
> > On May 1, 2014, at 8:51 AM, wrote:
> >
> > > Dell - Internal Use - Confidential
> > > I take it we were discussing the possibilities for high speed
> > > production logging. Previous people have rightly pointed out that a
> > > simplistic approach using soap might be ineffecient
> > >
> > > -----Original Message-----
> > > From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> > > Sent: Thursday, May 01, 2014 10:36 AM
> > > To: Log4J Users List
> > > Subject: Re: Web Service Appender
> > >
> > > Thats fine. I'm just not really sure what the question is any more.
> > >
> > > Ralph
> > >
> > > On May 1, 2014, at 8:22 AM, Walter_Marvin@DellTeam.com wrote:
> > >
> > >> Dell - Internal Use - Confidential
> > >> As I say there are a lot of architectural options. We need to
> > >> decide on
> > one. Having th ability to modify log4j should make whatever
> > architecture is chosen cleaner.
> > >>
> > >> Thanks
> > >>
> > >> Walter
> > >>
> > >> -----Original Message-----
> > >> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> > >> Sent: Thursday, May 01, 2014 10:16 AM
> > >> To: Log4J Users List
> > >> Subject: Re: Web Service Appender
> > >>
> > >> What you are describing is why I added the integration to Flume. It
> > >> is
> > very, very good at collecting log events and forwarding them. However,
> > you could use a JMS appender to write your events to the MQ queue.
> > >>
> > >> Ralph
> > >>
> > >> On May 1, 2014, at 7:15 AM, Evan J wrote:
> > >>
> > >>> Hi Ralph,
> > >>>
> > >>> All the request and response messages, some header data, with
> > >>> additional information, are placed in an MDC, packaged in an
> > >>> Appender and sent to an MQ queue which, ultimately, makes a call
> > >>> to the service. It's a centralized logging model for all the
> > >>> applications in a cluster. Frankly, I don't like the design nor
> > >>> the
> > setup, but I don't make such decisions (or requirements).
> > >>>
> > >>>
> > >>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
> > >>>
> > >>>> A web service to do what? Logging via SOAP would be extremely
> > >>>> slow if every log event is a single request. Can you elaborate on
> > >>>> what you really want to do?
> > >>>>
> > >>>> Ralph
> > >>>>
> > >>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
> > >>>>
> > >>>>> Thanks for verifying this. I thought I might be missing an
> > >>>>> obvious, and this has already been implemented by at least someone.
> > >>>>>
> > >>>>>
> > >>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
> > >>>> wrote:
> > >>>>>
> > >>>>>> Evan, no I'm not aware of any appender that logs to a web service.
> > >>>>>>
> > >>>>>>
> > >>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
> > >>>>>>
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>>> I searched around, but I could not find an off-the-shelf
> > >>>>>>> Appender that sends logs to a web service. Is there any?
> > >>>>>>>
> > >>>>>>
> > >>>>
> > >>>>
> > >>>> -----------------------------------------------------------------
> > >>>> --
> > >>>> -
> > >>>> - To unsubscribe, e-mail:
> > >>>> log4j-user-unsubscribe@logging.apache.org
> > >>>> For additional commands, e-mail:
> > >>>> log4j-user-help@logging.apache.org
> > >>>>
> > >>>>
> > >>
> > >>
> > >> -------------------------------------------------------------------
> > >> -- To unsubscribe, e-mail:
> > >> log4j-user-unsubscribe@logging.apache.org
> > >> For additional commands, e-mail: log4j-user-help@logging.apache.org
> > >
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > > For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
>
RE: Web Service Appender
Posted by Wa...@DellTeam.com.
Dell - Internal Use - Confidential
http://www.ibm.com/developerworks/library/ws-log4j/index.html
-----Original Message-----
From: Evan J [mailto:maps.this.address@gmail.com]
Sent: Monday, May 05, 2014 8:29 AM
To: Log4J Users List
Subject: Re: Web Service Appender
Hi Walter,
Can you point me to where one can try these freeware web service appenders?
Thanks.
On Mon, May 5, 2014 at 8:23 AM, wrote:
> Dell - Internal Use - Confidential
> I just saying we have the ability to work with log4j directly at this
> point. That should be useful since a custom appender will probably be
> needed for speed reasons, There are appenders for web services already
> written and available as freeware
>
> Thanks
>
> Walter
>
> -----Original Message-----
> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> Sent: Thursday, May 01, 2014 10:59 AM
> To: Log4J Users List
> Subject: Re: Web Service Appender
>
> This thread originally started to ask about logging to a web service
> (that term usually implies SOAP). It seems to have gone off into
> another direction and I'm not sure if there is still a question here
> someone wants answered. If you are making a proposal for an
> enhancement to Log4j 2 I am not sure what it is.
>
> Ralph
>
> On May 1, 2014, at 8:51 AM, wrote:
>
> > Dell - Internal Use - Confidential
> > I take it we were discussing the possibilities for high speed
> > production logging. Previous people have rightly pointed out that a
> > simplistic approach using soap might be ineffecient
> >
> > -----Original Message-----
> > From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> > Sent: Thursday, May 01, 2014 10:36 AM
> > To: Log4J Users List
> > Subject: Re: Web Service Appender
> >
> > Thats fine. I'm just not really sure what the question is any more.
> >
> > Ralph
> >
> > On May 1, 2014, at 8:22 AM, Walter_Marvin@DellTeam.com wrote:
> >
> >> Dell - Internal Use - Confidential
> >> As I say there are a lot of architectural options. We need to
> >> decide on
> one. Having th ability to modify log4j should make whatever
> architecture is chosen cleaner.
> >>
> >> Thanks
> >>
> >> Walter
> >>
> >> -----Original Message-----
> >> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> >> Sent: Thursday, May 01, 2014 10:16 AM
> >> To: Log4J Users List
> >> Subject: Re: Web Service Appender
> >>
> >> What you are describing is why I added the integration to Flume. It
> >> is
> very, very good at collecting log events and forwarding them. However,
> you could use a JMS appender to write your events to the MQ queue.
> >>
> >> Ralph
> >>
> >> On May 1, 2014, at 7:15 AM, Evan J wrote:
> >>
> >>> Hi Ralph,
> >>>
> >>> All the request and response messages, some header data, with
> >>> additional information, are placed in an MDC, packaged in an
> >>> Appender and sent to an MQ queue which, ultimately, makes a call
> >>> to the service. It's a centralized logging model for all the
> >>> applications in a cluster. Frankly, I don't like the design nor
> >>> the
> setup, but I don't make such decisions (or requirements).
> >>>
> >>>
> >>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
> >>>
> >>>> A web service to do what? Logging via SOAP would be extremely
> >>>> slow if every log event is a single request. Can you elaborate on
> >>>> what you really want to do?
> >>>>
> >>>> Ralph
> >>>>
> >>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
> >>>>
> >>>>> Thanks for verifying this. I thought I might be missing an
> >>>>> obvious, and this has already been implemented by at least someone.
> >>>>>
> >>>>>
> >>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
> >>>> wrote:
> >>>>>
> >>>>>> Evan, no I'm not aware of any appender that logs to a web service.
> >>>>>>
> >>>>>>
> >>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
> >>>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> I searched around, but I could not find an off-the-shelf
> >>>>>>> Appender that sends logs to a web service. Is there any?
> >>>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>> -----------------------------------------------------------------
> >>>> --
> >>>> -
> >>>> - To unsubscribe, e-mail:
> >>>> log4j-user-unsubscribe@logging.apache.org
> >>>> For additional commands, e-mail:
> >>>> log4j-user-help@logging.apache.org
> >>>>
> >>>>
> >>
> >>
> >> -------------------------------------------------------------------
> >> -- To unsubscribe, e-mail:
> >> log4j-user-unsubscribe@logging.apache.org
> >> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
Re: Web Service Appender
Posted by Evan J <ma...@gmail.com>.
Hi Walter,
Can you point me to where one can try these freeware web service appenders?
Thanks.
On Mon, May 5, 2014 at 8:23 AM, <Wa...@dellteam.com> wrote:
> Dell - Internal Use - Confidential
> I just saying we have the ability to work with log4j directly at this
> point. That should be useful since a custom appender will probably be
> needed for speed reasons,
> There are appenders for web services already written and available as
> freeware
>
> Thanks
>
> Walter
>
> -----Original Message-----
> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> Sent: Thursday, May 01, 2014 10:59 AM
> To: Log4J Users List
> Subject: Re: Web Service Appender
>
> This thread originally started to ask about logging to a web service (that
> term usually implies SOAP). It seems to have gone off into another
> direction and I'm not sure if there is still a question here someone wants
> answered. If you are making a proposal for an enhancement to Log4j 2 I am
> not sure what it is.
>
> Ralph
>
> On May 1, 2014, at 8:51 AM, wrote:
>
> > Dell - Internal Use - Confidential
> > I take it we were discussing the possibilities for high speed
> > production logging. Previous people have rightly pointed out that a
> > simplistic approach using soap might be ineffecient
> >
> > -----Original Message-----
> > From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> > Sent: Thursday, May 01, 2014 10:36 AM
> > To: Log4J Users List
> > Subject: Re: Web Service Appender
> >
> > Thats fine. I'm just not really sure what the question is any more.
> >
> > Ralph
> >
> > On May 1, 2014, at 8:22 AM, Walter_Marvin@DellTeam.com wrote:
> >
> >> Dell - Internal Use - Confidential
> >> As I say there are a lot of architectural options. We need to decide on
> one. Having th ability to modify log4j should make whatever architecture is
> chosen cleaner.
> >>
> >> Thanks
> >>
> >> Walter
> >>
> >> -----Original Message-----
> >> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> >> Sent: Thursday, May 01, 2014 10:16 AM
> >> To: Log4J Users List
> >> Subject: Re: Web Service Appender
> >>
> >> What you are describing is why I added the integration to Flume. It is
> very, very good at collecting log events and forwarding them. However, you
> could use a JMS appender to write your events to the MQ queue.
> >>
> >> Ralph
> >>
> >> On May 1, 2014, at 7:15 AM, Evan J wrote:
> >>
> >>> Hi Ralph,
> >>>
> >>> All the request and response messages, some header data, with
> >>> additional information, are placed in an MDC, packaged in an
> >>> Appender and sent to an MQ queue which, ultimately, makes a call to
> >>> the service. It's a centralized logging model for all the
> >>> applications in a cluster. Frankly, I don't like the design nor the
> setup, but I don't make such decisions (or requirements).
> >>>
> >>>
> >>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
> >>>
> >>>> A web service to do what? Logging via SOAP would be extremely slow
> >>>> if every log event is a single request. Can you elaborate on what
> >>>> you really want to do?
> >>>>
> >>>> Ralph
> >>>>
> >>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
> >>>>
> >>>>> Thanks for verifying this. I thought I might be missing an
> >>>>> obvious, and this has already been implemented by at least someone.
> >>>>>
> >>>>>
> >>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
> >>>> wrote:
> >>>>>
> >>>>>> Evan, no I'm not aware of any appender that logs to a web service.
> >>>>>>
> >>>>>>
> >>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
> >>>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> I searched around, but I could not find an off-the-shelf
> >>>>>>> Appender that sends logs to a web service. Is there any?
> >>>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> -
> >>>> - To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >>>>
> >>>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >> For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
RE: Web Service Appender
Posted by Wa...@DellTeam.com.
Dell - Internal Use - Confidential
I just saying we have the ability to work with log4j directly at this point. That should be useful since a custom appender will probably be needed for speed reasons,
There are appenders for web services already written and available as freeware
Thanks
Walter
-----Original Message-----
From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
Sent: Thursday, May 01, 2014 10:59 AM
To: Log4J Users List
Subject: Re: Web Service Appender
This thread originally started to ask about logging to a web service (that term usually implies SOAP). It seems to have gone off into another direction and I'm not sure if there is still a question here someone wants answered. If you are making a proposal for an enhancement to Log4j 2 I am not sure what it is.
Ralph
On May 1, 2014, at 8:51 AM, wrote:
> Dell - Internal Use - Confidential
> I take it we were discussing the possibilities for high speed
> production logging. Previous people have rightly pointed out that a
> simplistic approach using soap might be ineffecient
>
> -----Original Message-----
> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> Sent: Thursday, May 01, 2014 10:36 AM
> To: Log4J Users List
> Subject: Re: Web Service Appender
>
> Thats fine. I'm just not really sure what the question is any more.
>
> Ralph
>
> On May 1, 2014, at 8:22 AM, Walter_Marvin@DellTeam.com wrote:
>
>> Dell - Internal Use - Confidential
>> As I say there are a lot of architectural options. We need to decide on one. Having th ability to modify log4j should make whatever architecture is chosen cleaner.
>>
>> Thanks
>>
>> Walter
>>
>> -----Original Message-----
>> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
>> Sent: Thursday, May 01, 2014 10:16 AM
>> To: Log4J Users List
>> Subject: Re: Web Service Appender
>>
>> What you are describing is why I added the integration to Flume. It is very, very good at collecting log events and forwarding them. However, you could use a JMS appender to write your events to the MQ queue.
>>
>> Ralph
>>
>> On May 1, 2014, at 7:15 AM, Evan J wrote:
>>
>>> Hi Ralph,
>>>
>>> All the request and response messages, some header data, with
>>> additional information, are placed in an MDC, packaged in an
>>> Appender and sent to an MQ queue which, ultimately, makes a call to
>>> the service. It's a centralized logging model for all the
>>> applications in a cluster. Frankly, I don't like the design nor the setup, but I don't make such decisions (or requirements).
>>>
>>>
>>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
>>>
>>>> A web service to do what? Logging via SOAP would be extremely slow
>>>> if every log event is a single request. Can you elaborate on what
>>>> you really want to do?
>>>>
>>>> Ralph
>>>>
>>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
>>>>
>>>>> Thanks for verifying this. I thought I might be missing an
>>>>> obvious, and this has already been implemented by at least someone.
>>>>>
>>>>>
>>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
>>>> wrote:
>>>>>
>>>>>> Evan, no I'm not aware of any appender that logs to a web service.
>>>>>>
>>>>>>
>>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
>>>>>>
>>>>>> wrote:
>>>>>>
>>>>>>> I searched around, but I could not find an off-the-shelf
>>>>>>> Appender that sends logs to a web service. Is there any?
>>>>>>>
>>>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Web Service Appender
Posted by Ralph Goers <ra...@dslextreme.com>.
This thread originally started to ask about logging to a web service (that term usually implies SOAP). It seems to have gone off into another direction and I’m not sure if there is still a question here someone wants answered. If you are making a proposal for an enhancement to Log4j 2 I am not sure what it is.
Ralph
On May 1, 2014, at 8:51 AM, <Wa...@DellTeam.com> <Wa...@DellTeam.com> wrote:
> Dell - Internal Use - Confidential
> I take it we were discussing the possibilities for high speed production logging. Previous people have rightly pointed out that a simplistic approach using soap might be ineffecient
>
> -----Original Message-----
> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> Sent: Thursday, May 01, 2014 10:36 AM
> To: Log4J Users List
> Subject: Re: Web Service Appender
>
> Thats fine. I'm just not really sure what the question is any more.
>
> Ralph
>
> On May 1, 2014, at 8:22 AM, Walter_Marvin@DellTeam.com wrote:
>
>> Dell - Internal Use - Confidential
>> As I say there are a lot of architectural options. We need to decide on one. Having th ability to modify log4j should make whatever architecture is chosen cleaner.
>>
>> Thanks
>>
>> Walter
>>
>> -----Original Message-----
>> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
>> Sent: Thursday, May 01, 2014 10:16 AM
>> To: Log4J Users List
>> Subject: Re: Web Service Appender
>>
>> What you are describing is why I added the integration to Flume. It is very, very good at collecting log events and forwarding them. However, you could use a JMS appender to write your events to the MQ queue.
>>
>> Ralph
>>
>> On May 1, 2014, at 7:15 AM, Evan J wrote:
>>
>>> Hi Ralph,
>>>
>>> All the request and response messages, some header data, with
>>> additional information, are placed in an MDC, packaged in an Appender
>>> and sent to an MQ queue which, ultimately, makes a call to the
>>> service. It's a centralized logging model for all the applications in
>>> a cluster. Frankly, I don't like the design nor the setup, but I don't make such decisions (or requirements).
>>>
>>>
>>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
>>>
>>>> A web service to do what? Logging via SOAP would be extremely slow
>>>> if every log event is a single request. Can you elaborate on what
>>>> you really want to do?
>>>>
>>>> Ralph
>>>>
>>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
>>>>
>>>>> Thanks for verifying this. I thought I might be missing an obvious,
>>>>> and this has already been implemented by at least someone.
>>>>>
>>>>>
>>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
>>>> wrote:
>>>>>
>>>>>> Evan, no I'm not aware of any appender that logs to a web service.
>>>>>>
>>>>>>
>>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
>>>>>>
>>>>>> wrote:
>>>>>>
>>>>>>> I searched around, but I could not find an off-the-shelf Appender
>>>>>>> that sends logs to a web service. Is there any?
>>>>>>>
>>>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
RE: Web Service Appender
Posted by Wa...@DellTeam.com.
Dell - Internal Use - Confidential
I take it we were discussing the possibilities for high speed production logging. Previous people have rightly pointed out that a simplistic approach using soap might be ineffecient
-----Original Message-----
From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
Sent: Thursday, May 01, 2014 10:36 AM
To: Log4J Users List
Subject: Re: Web Service Appender
Thats fine. I'm just not really sure what the question is any more.
Ralph
On May 1, 2014, at 8:22 AM, Walter_Marvin@DellTeam.com wrote:
> Dell - Internal Use - Confidential
> As I say there are a lot of architectural options. We need to decide on one. Having th ability to modify log4j should make whatever architecture is chosen cleaner.
>
> Thanks
>
> Walter
>
> -----Original Message-----
> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> Sent: Thursday, May 01, 2014 10:16 AM
> To: Log4J Users List
> Subject: Re: Web Service Appender
>
> What you are describing is why I added the integration to Flume. It is very, very good at collecting log events and forwarding them. However, you could use a JMS appender to write your events to the MQ queue.
>
> Ralph
>
> On May 1, 2014, at 7:15 AM, Evan J wrote:
>
>> Hi Ralph,
>>
>> All the request and response messages, some header data, with
>> additional information, are placed in an MDC, packaged in an Appender
>> and sent to an MQ queue which, ultimately, makes a call to the
>> service. It's a centralized logging model for all the applications in
>> a cluster. Frankly, I don't like the design nor the setup, but I don't make such decisions (or requirements).
>>
>>
>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
>>
>>> A web service to do what? Logging via SOAP would be extremely slow
>>> if every log event is a single request. Can you elaborate on what
>>> you really want to do?
>>>
>>> Ralph
>>>
>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
>>>
>>>> Thanks for verifying this. I thought I might be missing an obvious,
>>>> and this has already been implemented by at least someone.
>>>>
>>>>
>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
>>> wrote:
>>>>
>>>>> Evan, no I'm not aware of any appender that logs to a web service.
>>>>>
>>>>>
>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
>>>>>
>>>>> wrote:
>>>>>
>>>>>> I searched around, but I could not find an off-the-shelf Appender
>>>>>> that sends logs to a web service. Is there any?
>>>>>>
>>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Web Service Appender
Posted by Ralph Goers <ra...@dslextreme.com>.
Thats fine. I’m just not really sure what the question is any more.
Ralph
On May 1, 2014, at 8:22 AM, Walter_Marvin@DellTeam.com wrote:
> Dell - Internal Use - Confidential
> As I say there are a lot of architectural options. We need to decide on one. Having th ability to modify log4j should make whatever architecture is chosen cleaner.
>
> Thanks
>
> Walter
>
> -----Original Message-----
> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> Sent: Thursday, May 01, 2014 10:16 AM
> To: Log4J Users List
> Subject: Re: Web Service Appender
>
> What you are describing is why I added the integration to Flume. It is very, very good at collecting log events and forwarding them. However, you could use a JMS appender to write your events to the MQ queue.
>
> Ralph
>
> On May 1, 2014, at 7:15 AM, Evan J wrote:
>
>> Hi Ralph,
>>
>> All the request and response messages, some header data, with
>> additional information, are placed in an MDC, packaged in an Appender
>> and sent to an MQ queue which, ultimately, makes a call to the
>> service. It's a centralized logging model for all the applications in
>> a cluster. Frankly, I don't like the design nor the setup, but I don't make such decisions (or requirements).
>>
>>
>> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
>>
>>> A web service to do what? Logging via SOAP would be extremely slow if
>>> every log event is a single request. Can you elaborate on what you really
>>> want to do?
>>>
>>> Ralph
>>>
>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
>>>
>>>> Thanks for verifying this. I thought I might be missing an obvious,
>>>> and this has already been implemented by at least someone.
>>>>
>>>>
>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
>>> wrote:
>>>>
>>>>> Evan, no I'm not aware of any appender that logs to a web service.
>>>>>
>>>>>
>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
>>>>>
>>>>> wrote:
>>>>>
>>>>>> I searched around, but I could not find an off-the-shelf Appender
>>>>>> that sends logs to a web service. Is there any?
>>>>>>
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
RE: Web Service Appender
Posted by Wa...@DellTeam.com.
Dell - Internal Use - Confidential
As I say there are a lot of architectural options. We need to decide on one. Having th ability to modify log4j should make whatever architecture is chosen cleaner.
Thanks
Walter
-----Original Message-----
From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
Sent: Thursday, May 01, 2014 10:16 AM
To: Log4J Users List
Subject: Re: Web Service Appender
What you are describing is why I added the integration to Flume. It is very, very good at collecting log events and forwarding them. However, you could use a JMS appender to write your events to the MQ queue.
Ralph
On May 1, 2014, at 7:15 AM, Evan J wrote:
> Hi Ralph,
>
> All the request and response messages, some header data, with
> additional information, are placed in an MDC, packaged in an Appender
> and sent to an MQ queue which, ultimately, makes a call to the
> service. It's a centralized logging model for all the applications in
> a cluster. Frankly, I don't like the design nor the setup, but I don't make such decisions (or requirements).
>
>
> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers wrote:
>
>> A web service to do what? Logging via SOAP would be extremely slow if
>> every log event is a single request. Can you elaborate on what you really
>> want to do?
>>
>> Ralph
>>
>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
>>
>>> Thanks for verifying this. I thought I might be missing an obvious,
>>> and this has already been implemented by at least someone.
>>>
>>>
>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
>> wrote:
>>>
>>>> Evan, no I'm not aware of any appender that logs to a web service.
>>>>
>>>>
>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
>>>>
>>>> wrote:
>>>>
>>>>> I searched around, but I could not find an off-the-shelf Appender
>>>>> that sends logs to a web service. Is there any?
>>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Web Service Appender
Posted by Ralph Goers <ra...@dslextreme.com>.
What you are describing is why I added the integration to Flume. It is very, very good at collecting log events and forwarding them. However, you could use a JMS appender to write your events to the MQ queue.
Ralph
On May 1, 2014, at 7:15 AM, Evan J <ma...@gmail.com> wrote:
> Hi Ralph,
>
> All the request and response messages, some header data, with additional
> information, are placed in an MDC, packaged in an Appender and sent to an
> MQ queue which, ultimately, makes a call to the service. It's a centralized
> logging model for all the applications in a cluster. Frankly, I don't like
> the design nor the setup, but I don't make such decisions (or requirements).
>
>
> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers <ra...@dslextreme.com>wrote:
>
>> A web service to do what? Logging via SOAP would be extremely slow if
>> every log event is a single request. Can you elaborate on what you really
>> want to do?
>>
>> Ralph
>>
>> On Apr 30, 2014, at 9:10 PM, Evan J <ma...@gmail.com> wrote:
>>
>>> Thanks for verifying this. I thought I might be missing an obvious, and
>>> this has already been implemented by at least someone.
>>>
>>>
>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma <re...@gmail.com>
>> wrote:
>>>
>>>> Evan, no I'm not aware of any appender that logs to a web service.
>>>>
>>>>
>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J <ma...@gmail.com>
>>>> wrote:
>>>>
>>>>> I searched around, but I could not find an off-the-shelf Appender that
>>>>> sends logs to a web service. Is there any?
>>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
RE: Web Service Appender
Posted by Wa...@DellTeam.com.
Dell - Internal Use - Confidential
There are several architectural options . The cleanest might be to make a custom appender, and then do the queue removal and transport with a thread within
Log4j itself. This has the advantage of not disturbing the current setup and interface for local logging for development, while still providing a "high speed" method for production logging. In this case JMS would not be used, rather internal java queuing could be used, and the results put to a database, ready to be retrieved by a servlet and rich faces client. We have the technology to do this, since I am about to demonstrate a debuggable log4j built from source code. At the point we modify log4j, we would of course have to bring it under configuration management. The main problems is that it is a bit of work, and we would have to determine the correct internal queue size so that bursts of logging could be accomplished without slowing down the main processes. The Idea is to overlap I/O and CPU intensive processing so as to make the OS process our data as efficiently as possible. To this end, the database load could be done on other processors, perhaps using tux.
Thanks
Walter
-----Original Message-----
From: Gary Gregory [mailto:garydgregory@gmail.com]
Sent: Thursday, May 01, 2014 9:28 AM
To: Log4J Users List
Subject: Re: Web Service Appender
So the app logs to JMS, not SOAP. Later you have something else that consumes the queue and calls the WS, but that would not be done by Log4j.
Or are you suggesting that Log4j should be able to consume from a Q and call a WS?
Gary
On Thu, May 1, 2014 at 10:15 AM, Evan J wrote:
> Hi Ralph,
>
> All the request and response messages, some header data, with
> additional information, are placed in an MDC, packaged in an Appender
> and sent to an MQ queue which, ultimately, makes a call to the
> service. It's a centralized logging model for all the applications in
> a cluster. Frankly, I don't like the design nor the setup, but I don't
> make such decisions (or requirements).
>
>
> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers
> <ralph.goers@dslextreme.com
> >wrote:
>
> > A web service to do what? Logging via SOAP would be extremely slow if
> > every log event is a single request. Can you elaborate on what you
> really
> > want to do?
> >
> > Ralph
> >
> > On Apr 30, 2014, at 9:10 PM, Evan J wrote:
> >
> > > Thanks for verifying this. I thought I might be missing an
> > > obvious, and this has already been implemented by at least someone.
> > >
> > >
> > > On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma
> > >
> > wrote:
> > >
> > >> Evan, no I'm not aware of any appender that logs to a web service.
> > >>
> > >>
> > >> On Thu, May 1, 2014 at 9:21 AM, Evan J
> > >>
> > >> wrote:
> > >>
> > >>> I searched around, but I could not find an off-the-shelf
> > >>> Appender
> that
> > >>> sends logs to a web service. Is there any?
> > >>>
> > >>
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: Web Service Appender
Posted by Gary Gregory <ga...@gmail.com>.
So the app logs to JMS, not SOAP. Later you have something else that
consumes the queue and calls the WS, but that would not be done by Log4j.
Or are you suggesting that Log4j should be able to consume from a Q and
call a WS?
Gary
On Thu, May 1, 2014 at 10:15 AM, Evan J <ma...@gmail.com> wrote:
> Hi Ralph,
>
> All the request and response messages, some header data, with additional
> information, are placed in an MDC, packaged in an Appender and sent to an
> MQ queue which, ultimately, makes a call to the service. It's a centralized
> logging model for all the applications in a cluster. Frankly, I don't like
> the design nor the setup, but I don't make such decisions (or
> requirements).
>
>
> On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers <ralph.goers@dslextreme.com
> >wrote:
>
> > A web service to do what? Logging via SOAP would be extremely slow if
> > every log event is a single request. Can you elaborate on what you
> really
> > want to do?
> >
> > Ralph
> >
> > On Apr 30, 2014, at 9:10 PM, Evan J <ma...@gmail.com> wrote:
> >
> > > Thanks for verifying this. I thought I might be missing an obvious, and
> > > this has already been implemented by at least someone.
> > >
> > >
> > > On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma <re...@gmail.com>
> > wrote:
> > >
> > >> Evan, no I'm not aware of any appender that logs to a web service.
> > >>
> > >>
> > >> On Thu, May 1, 2014 at 9:21 AM, Evan J <ma...@gmail.com>
> > >> wrote:
> > >>
> > >>> I searched around, but I could not find an off-the-shelf Appender
> that
> > >>> sends logs to a web service. Is there any?
> > >>>
> > >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: Web Service Appender
Posted by Evan J <ma...@gmail.com>.
Hi Ralph,
All the request and response messages, some header data, with additional
information, are placed in an MDC, packaged in an Appender and sent to an
MQ queue which, ultimately, makes a call to the service. It's a centralized
logging model for all the applications in a cluster. Frankly, I don't like
the design nor the setup, but I don't make such decisions (or requirements).
On Wed, Apr 30, 2014 at 11:15 PM, Ralph Goers <ra...@dslextreme.com>wrote:
> A web service to do what? Logging via SOAP would be extremely slow if
> every log event is a single request. Can you elaborate on what you really
> want to do?
>
> Ralph
>
> On Apr 30, 2014, at 9:10 PM, Evan J <ma...@gmail.com> wrote:
>
> > Thanks for verifying this. I thought I might be missing an obvious, and
> > this has already been implemented by at least someone.
> >
> >
> > On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma <re...@gmail.com>
> wrote:
> >
> >> Evan, no I'm not aware of any appender that logs to a web service.
> >>
> >>
> >> On Thu, May 1, 2014 at 9:21 AM, Evan J <ma...@gmail.com>
> >> wrote:
> >>
> >>> I searched around, but I could not find an off-the-shelf Appender that
> >>> sends logs to a web service. Is there any?
> >>>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
RE: Web Service Appender
Posted by Wa...@DellTeam.com.
Dell - Internal Use - Confidential
What is needed is not only bundling which is a form of buffering, but also process overlap so that the transfers are held up to a point where the processing is more quiet
And more cycles are available. Offloading to another processor using tux also accomplishes this. This buffering could involve a stop and wait type protocol with a retransmit feature. The transmit would have to be some form of permanent storage to do this. Queuing offers the opportunity to "bundle" in memory, but might result in message loss if some permanent storage is also not involved, when a process aborts.
-----Original Message-----
From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
Sent: Thursday, May 01, 2014 10:18 AM
To: Log4J Users List
Subject: Re: Web Service Appender
I guarantee you, on a busy system with lots of logging sending a SOAP message for every event will be a problem. If they are being bundled so that multiple events are sent in each request that will perform better but could result in losing all the events that are buffered.
Ralph
On May 1, 2014, at 7:26 AM, Walter_Marvin@DellTeam.com wrote:
> Dell - Internal Use - Confidential
> Not necessarily. Remember that the people who read these logs are not
> in the processing loop, and therefore do not slow down the process,
> What is required is an asynchronous thread or process to do the soap transfer during off cycles, and storage to receive the messages from the Processing stream. Some sort of queuing and thread, or database storage might be used.
>
> -----Original Message-----
> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> Sent: Wednesday, April 30, 2014 11:16 PM
> To: Log4J Users List
> Subject: Re: Web Service Appender
>
> A web service to do what? Logging via SOAP would be extremely slow if every log event is a single request. Can you elaborate on what you really want to do?
>
> Ralph
>
> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
>
>> Thanks for verifying this. I thought I might be missing an obvious,
>> and this has already been implemented by at least someone.
>>
>>
>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma wrote:
>>
>>> Evan, no I'm not aware of any appender that logs to a web service.
>>>
>>>
>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
>>> wrote:
>>>
>>>> I searched around, but I could not find an off-the-shelf Appender
>>>> that sends logs to a web service. Is there any?
>>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Web Service Appender
Posted by Ralph Goers <ra...@dslextreme.com>.
Yes, persistent buffering can prevent the data loss but adds to the complexity. The Flume Appender does that.
I will take a look at the scribe appender when I get a chance.
Ralph
On May 1, 2014, at 8:39 AM, Michael Wechner <mi...@wyona.com> wrote:
> Am 01.05.14 17:18, schrieb Ralph Goers:
>> I guarantee you, on a busy system with lots of logging sending a SOAP message for every event will be a problem.
>
> I can second/confirm that.
>
> We have developed such an appender in order to log user requests for
> user tracking and personalization
>
> https://github.com/wyona/yanel/blob/master/conf/log4j.properties
>
> whereas see the boosthttp configuration
>> If they are being bundled so that multiple events are sent in each request that will perform better
>
> yes, that's what we do
>> but could result in losing all the events that are buffered.
>
> one can buffer them persistently, or do I misunderstand you?
>
> I am not sure whether "refactoring"
> https://github.com/joshdevins/log4j-scribe-appender might make sense, but
> it probably makes sense to have a look at it.
>
> HTH
>
> Michael
>>
>> Ralph
>>
>>
>> On May 1, 2014, at 7:26 AM, Walter_Marvin@DellTeam.com wrote:
>>
>>> Dell - Internal Use - Confidential
>>> Not necessarily. Remember that the people who read these logs are not in the processing loop, and therefore do not slow down the process,
>>> What is required is an asynchronous thread or process to do the soap transfer during off cycles, and storage to receive the messages from the
>>> Processing stream. Some sort of queuing and thread, or database storage might be used.
>>>
>>> -----Original Message-----
>>> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
>>> Sent: Wednesday, April 30, 2014 11:16 PM
>>> To: Log4J Users List
>>> Subject: Re: Web Service Appender
>>>
>>> A web service to do what? Logging via SOAP would be extremely slow if every log event is a single request. Can you elaborate on what you really want to do?
>>>
>>> Ralph
>>>
>>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
>>>
>>>> Thanks for verifying this. I thought I might be missing an obvious,
>>>> and this has already been implemented by at least someone.
>>>>
>>>>
>>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma wrote:
>>>>
>>>>> Evan, no I'm not aware of any appender that logs to a web service.
>>>>>
>>>>>
>>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
>>>>> wrote:
>>>>>
>>>>>> I searched around, but I could not find an off-the-shelf Appender
>>>>>> that sends logs to a web service. Is there any?
>>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Web Service Appender
Posted by Michael Wechner <mi...@wyona.com>.
Am 01.05.14 17:18, schrieb Ralph Goers:
> I guarantee you, on a busy system with lots of logging sending a SOAP message for every event will be a problem.
I can second/confirm that.
We have developed such an appender in order to log user requests for
user tracking and personalization
https://github.com/wyona/yanel/blob/master/conf/log4j.properties
whereas see the boosthttp configuration
> If they are being bundled so that multiple events are sent in each request that will perform better
yes, that's what we do
> but could result in losing all the events that are buffered.
one can buffer them persistently, or do I misunderstand you?
I am not sure whether "refactoring"
https://github.com/joshdevins/log4j-scribe-appender might make sense, but
it probably makes sense to have a look at it.
HTH
Michael
>
> Ralph
>
>
> On May 1, 2014, at 7:26 AM, Walter_Marvin@DellTeam.com wrote:
>
>> Dell - Internal Use - Confidential
>> Not necessarily. Remember that the people who read these logs are not in the processing loop, and therefore do not slow down the process,
>> What is required is an asynchronous thread or process to do the soap transfer during off cycles, and storage to receive the messages from the
>> Processing stream. Some sort of queuing and thread, or database storage might be used.
>>
>> -----Original Message-----
>> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
>> Sent: Wednesday, April 30, 2014 11:16 PM
>> To: Log4J Users List
>> Subject: Re: Web Service Appender
>>
>> A web service to do what? Logging via SOAP would be extremely slow if every log event is a single request. Can you elaborate on what you really want to do?
>>
>> Ralph
>>
>> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
>>
>>> Thanks for verifying this. I thought I might be missing an obvious,
>>> and this has already been implemented by at least someone.
>>>
>>>
>>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma wrote:
>>>
>>>> Evan, no I'm not aware of any appender that logs to a web service.
>>>>
>>>>
>>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
>>>> wrote:
>>>>
>>>>> I searched around, but I could not find an off-the-shelf Appender
>>>>> that sends logs to a web service. Is there any?
>>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Web Service Appender
Posted by Ralph Goers <ra...@dslextreme.com>.
I guarantee you, on a busy system with lots of logging sending a SOAP message for every event will be a problem. If they are being bundled so that multiple events are sent in each request that will perform better but could result in losing all the events that are buffered.
Ralph
On May 1, 2014, at 7:26 AM, Walter_Marvin@DellTeam.com wrote:
> Dell - Internal Use - Confidential
> Not necessarily. Remember that the people who read these logs are not in the processing loop, and therefore do not slow down the process,
> What is required is an asynchronous thread or process to do the soap transfer during off cycles, and storage to receive the messages from the
> Processing stream. Some sort of queuing and thread, or database storage might be used.
>
> -----Original Message-----
> From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
> Sent: Wednesday, April 30, 2014 11:16 PM
> To: Log4J Users List
> Subject: Re: Web Service Appender
>
> A web service to do what? Logging via SOAP would be extremely slow if every log event is a single request. Can you elaborate on what you really want to do?
>
> Ralph
>
> On Apr 30, 2014, at 9:10 PM, Evan J wrote:
>
>> Thanks for verifying this. I thought I might be missing an obvious,
>> and this has already been implemented by at least someone.
>>
>>
>> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma wrote:
>>
>>> Evan, no I'm not aware of any appender that logs to a web service.
>>>
>>>
>>> On Thu, May 1, 2014 at 9:21 AM, Evan J
>>> wrote:
>>>
>>>> I searched around, but I could not find an off-the-shelf Appender
>>>> that sends logs to a web service. Is there any?
>>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
RE: Web Service Appender
Posted by Wa...@DellTeam.com.
Dell - Internal Use - Confidential
Not necessarily. Remember that the people who read these logs are not in the processing loop, and therefore do not slow down the process,
What is required is an asynchronous thread or process to do the soap transfer during off cycles, and storage to receive the messages from the
Processing stream. Some sort of queuing and thread, or database storage might be used.
-----Original Message-----
From: Ralph Goers [mailto:ralph.goers@dslextreme.com]
Sent: Wednesday, April 30, 2014 11:16 PM
To: Log4J Users List
Subject: Re: Web Service Appender
A web service to do what? Logging via SOAP would be extremely slow if every log event is a single request. Can you elaborate on what you really want to do?
Ralph
On Apr 30, 2014, at 9:10 PM, Evan J wrote:
> Thanks for verifying this. I thought I might be missing an obvious,
> and this has already been implemented by at least someone.
>
>
> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma wrote:
>
>> Evan, no I'm not aware of any appender that logs to a web service.
>>
>>
>> On Thu, May 1, 2014 at 9:21 AM, Evan J
>> wrote:
>>
>>> I searched around, but I could not find an off-the-shelf Appender
>>> that sends logs to a web service. Is there any?
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Web Service Appender
Posted by Ralph Goers <ra...@dslextreme.com>.
A web service to do what? Logging via SOAP would be extremely slow if every log event is a single request. Can you elaborate on what you really want to do?
Ralph
On Apr 30, 2014, at 9:10 PM, Evan J <ma...@gmail.com> wrote:
> Thanks for verifying this. I thought I might be missing an obvious, and
> this has already been implemented by at least someone.
>
>
> On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma <re...@gmail.com> wrote:
>
>> Evan, no I'm not aware of any appender that logs to a web service.
>>
>>
>> On Thu, May 1, 2014 at 9:21 AM, Evan J <ma...@gmail.com>
>> wrote:
>>
>>> I searched around, but I could not find an off-the-shelf Appender that
>>> sends logs to a web service. Is there any?
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Web Service Appender
Posted by Evan J <ma...@gmail.com>.
Thanks for verifying this. I thought I might be missing an obvious, and
this has already been implemented by at least someone.
On Wed, Apr 30, 2014 at 7:48 PM, Remko Popma <re...@gmail.com> wrote:
> Evan, no I'm not aware of any appender that logs to a web service.
>
>
> On Thu, May 1, 2014 at 9:21 AM, Evan J <ma...@gmail.com>
> wrote:
>
> > I searched around, but I could not find an off-the-shelf Appender that
> > sends logs to a web service. Is there any?
> >
>
Re: Web Service Appender
Posted by Remko Popma <re...@gmail.com>.
Evan, no I'm not aware of any appender that logs to a web service.
On Thu, May 1, 2014 at 9:21 AM, Evan J <ma...@gmail.com> wrote:
> I searched around, but I could not find an off-the-shelf Appender that
> sends logs to a web service. Is there any?
>