Return-Path: X-Original-To: apmail-logging-log4j-user-archive@www.apache.org Delivered-To: apmail-logging-log4j-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BC3E511873 for ; Fri, 2 May 2014 19:16:21 +0000 (UTC) Received: (qmail 36412 invoked by uid 500); 2 May 2014 19:14:07 -0000 Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org Received: (qmail 36128 invoked by uid 500); 2 May 2014 19:13:45 -0000 Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@logging.apache.org Received: (qmail 35858 invoked by uid 99); 2 May 2014 19:13:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 May 2014 19:13:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of boards@gmail.com designates 209.85.214.174 as permitted sender) Received: from [209.85.214.174] (HELO mail-ob0-f174.google.com) (209.85.214.174) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 May 2014 19:13:22 +0000 Received: by mail-ob0-f174.google.com with SMTP id gq1so5736574obb.33 for ; Fri, 02 May 2014 12:12:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=/qWcl3LakopDTwo6WkOJdnqUrUtixWWciCU7sV+txpY=; b=LPuB+crb0ROjjjcm+Wex5PC9yd/y6duLg02w4VV2elKakpfSe605NEqmjVQJOlcUbe J4H11LnlyHg+4Qvxq0KfjKu6/2hGMIrHjUALGEKeaXf005ebTrRzKa6NJjMJddxd/ga8 QwFWKvhquobzeBTZCHY9VDl6yrGwhozWBqsV44jnRjA2RK4CKCaU3HvwPThntLwbCgjY CUwVqf1XRrIWb0jFOMZM3rwAsqQDaMWmd182Bftb4XvRDFny3j5d4WlJy3GTVJhHheHH kkKO9mvtrEu4E06b304Ga7Lj/oGucw8/Z57bcennZrxz6wZpWeRvS/Vdo467waoblNwD zOqA== MIME-Version: 1.0 X-Received: by 10.182.115.232 with SMTP id jr8mr5962406obb.35.1399057979084; Fri, 02 May 2014 12:12:59 -0700 (PDT) Received: by 10.76.72.68 with HTTP; Fri, 2 May 2014 12:12:58 -0700 (PDT) In-Reply-To: References: <641BF779-851D-491F-A7A3-FB8901435279@dslextreme.com> <3ECFE551-06A6-4D93-9B9A-0CB98241C680@dslextreme.com> <6DE89D99-0CF7-4944-90EE-7EAAD9C1EED9@dslextreme.com> Date: Fri, 2 May 2014 14:12:58 -0500 Message-ID: Subject: Re: Web Service Appender From: Matt Sicker To: Log4J Users List Content-Type: multipart/alternative; boundary=089e011762f9dd15c404f86f9144 X-Virus-Checked: Checked by ClamAV on apache.org --089e011762f9dd15c404f86f9144 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Wow I can't type good. Thanks. On 1 May 2014 21:42, Ralph Goers wrote: > Flume, not Felix. > > Sent from my iPad > > > On May 1, 2014, at 1:28 PM, Matt Sicker 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 fo= r > > 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 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 simp= ly > >> make use of JMSAppender to put messages on a queue and have JMS client= s > >> 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 o= f > 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=E2=80=99m 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 decid= e > >> 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 slo= w > >>>>>>> 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 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org > For additional commands, e-mail: log4j-user-help@logging.apache.org > > --=20 Matt Sicker --089e011762f9dd15c404f86f9144--