Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5B52218B63 for ; Thu, 11 Jun 2015 19:28:06 +0000 (UTC) Received: (qmail 91707 invoked by uid 500); 11 Jun 2015 19:28:05 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 91657 invoked by uid 500); 11 Jun 2015 19:28:05 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 91645 invoked by uid 99); 11 Jun 2015 19:28:05 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jun 2015 19:28:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D169BC0B03 for ; Thu, 11 Jun 2015 19:28:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.193 X-Spam-Level: * X-Spam-Status: No, score=1.193 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id vtos1VoFUdWm for ; Thu, 11 Jun 2015 19:27:56 +0000 (UTC) Received: from mail-wg0-f68.google.com (mail-wg0-f68.google.com [74.125.82.68]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 5FA4F453C8 for ; Thu, 11 Jun 2015 19:27:56 +0000 (UTC) Received: by wggz12 with SMTP id z12so803576wgg.1 for ; Thu, 11 Jun 2015 12:27:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=zTTU4kDz56YuzQiMvWRQlAKc/0dG2QPTFAsTIH2gPcg=; b=GXoCCd2wZebIyzSyf64579v9Pl96TJC7BpiHlXqpmi+OtrnNxlbbVCyFzPrNVDfhFq 9GacqTuePWzCE1wYNRUePdO9vrGNpkzuRWs5Eez0XNwl14iBwDG9whpC3hPp/mtxC3mD gJFl/19a2VpqPEvhw8i7m2BgWyZ3/++PY12fvbZVGu4UqcqAuZeQYOFtQLFbhjhe2Klc Rt5t+mbMgCu/JdvXB3zRuhtvDYY3S5gOR5WwOkFest+QDo2CsrRqy2e6Ndczhu1OfWVL UzAfRVu+Et2DsfsOFUcCuS8X+FQMlHWr0umy5oXVHPRKr9JHCAzvczvFImDnJxbLOM8Y /UoQ== X-Received: by 10.194.89.70 with SMTP id bm6mr18460390wjb.146.1434050875596; Thu, 11 Jun 2015 12:27:55 -0700 (PDT) Received: from timbomac.home (host86-144-45-252.range86-144.btcentralplus.com. [86.144.45.252]) by mx.google.com with ESMTPSA id ej5sm2458150wjd.22.2015.06.11.12.27.53 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jun 2015 12:27:54 -0700 (PDT) Message-ID: <5579E138.5070402@gmail.com> Date: Thu, 11 Jun 2015 20:27:52 +0100 From: Tim Dudgeon User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: users@camel.apache.org Subject: Re: Trace from and to endpoints References: <1433951510661-5768077.post@n5.nabble.com> In-Reply-To: <1433951510661-5768077.post@n5.nabble.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit I believe Camel tracks this automatically at the exchange level (assuming you are wanting this on a per-exchange basis). e.g. when you get an exception this information is written to the logs, so its already there. Try looking at the Exchange properties. Tim On 10/06/2015 16:51, rwijngaa wrote: > Hi, > > What would be the best way to gather the 'path' a camel route takes for an > audit log. > The way i see it i have at least 3 options: implement my own Tracer > (http://camel.apache.org/tracer.html), implement my own InterceptStrategy or > catch the exchange events by extending the EventNotifierSupport? > > Thanks in advance > Regards > Rino > > > > -- > View this message in context: http://camel.465427.n5.nabble.com/Trace-from-and-to-endpoints-tp5768077.html > Sent from the Camel - Users mailing list archive at Nabble.com.