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 EAA2B18124 for ; Wed, 24 Feb 2016 11:35:30 +0000 (UTC) Received: (qmail 82221 invoked by uid 500); 24 Feb 2016 11:34:56 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 82169 invoked by uid 500); 24 Feb 2016 11:34:56 -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 82156 invoked by uid 99); 24 Feb 2016 11:34:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Feb 2016 11:34:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 673731804EF for ; Wed, 24 Feb 2016 11:34:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.802 X-Spam-Level: X-Spam-Status: No, score=-0.802 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id LE4_Eqgi1OF4 for ; Wed, 24 Feb 2016 11:34:54 +0000 (UTC) Received: from mail-io0-f181.google.com (mail-io0-f181.google.com [209.85.223.181]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id C9E225FABF for ; Wed, 24 Feb 2016 11:34:53 +0000 (UTC) Received: by mail-io0-f181.google.com with SMTP id l127so32676019iof.3 for ; Wed, 24 Feb 2016 03:34:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=o6qTwqy52XwQsVcBosRW33JmNuiczdXb2ENgvL3eMbA=; b=D92zhfdhYa2wdzkW5v1Eang+kAoNU8Q9lTaN1Ww/O0AXK+Wky4YiCZ3dqtxxrvH+oh t6kPW/JRrz8HHJIRLuBzEGeNZCXhSqJJkWhmgKOTPzQ5kmQ/PR89opykGinC/ImNmIHb nCQIYDbuqGGguMpEog/ROpnSjJEg4qrE6cCMaTSfl5szegkS9yk9rIpGnnSsFW0PBZ5Y YxgwjFUL17f4W1O3fttV+uBmpj+TFnY9dN8VipdfIAWDY9uRTVKE/k05GuBVUB8KxcWl yNn45L1q/P2mG4iCITnm4h8fi8WYVvRtLR2Bh3ju72xKbDmQFZEflrbtgKBmr16PDVwK 8iNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=o6qTwqy52XwQsVcBosRW33JmNuiczdXb2ENgvL3eMbA=; b=Hrd4FSDaok3DN6OaF9JCzWnbAbC/JFXOF4clM9rnNzsAOaGXPUIRd+AkVZWCdCW8N+ VhuK0gbl9cVHiTa0v8bJzlzaNyx45DSYXdF/hGoYGvVUnRAE+8CEqgTovHYufDyz1XRU CW4CqhLO9UVncYIS733KsmCLPVvXdIJh/uuS2ewmpN+8oOS1vG8J/ztsZkwAqM4UEo6P KViOHJjIj2QDPCV276M5dMcMyEJ03Zop1v1IZsQCFuTC9jEq6IEPrOaKy1NsVu7WdF/b s+jKkq6ANUi4DcrtZQUdPRpqg8VimTl25ZIGWSHtwxIE8cersGFZHzUkPaDEL1kQH5oL iofg== X-Gm-Message-State: AG10YOTbeKAg+WMs3qjHYAqgJ31bDfiJUCE8pXUklPYxgbiycPv3GUkvrcWCWRrQ4vk8H1qLCKAz/IBTWtCVCw== X-Received: by 10.107.159.148 with SMTP id i142mr1737106ioe.29.1456313692754; Wed, 24 Feb 2016 03:34:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.0.211 with HTTP; Wed, 24 Feb 2016 03:34:33 -0800 (PST) In-Reply-To: References: From: Claus Ibsen Date: Wed, 24 Feb 2016 12:34:33 +0100 Message-ID: Subject: Re: Use Simple to log Message History? To: "users@camel.apache.org" Content-Type: text/plain; charset=UTF-8 You can use the tracer http://camel.apache.org/tracer On Wed, Feb 24, 2016 at 12:12 PM, James Green wrote: > Our use-case was in debugging why a processor was being triggered twice. We > wanted to log immediately before the processor to see where the Exchange > came from second time around. > > I see a few people via Google asking how to log where the Exchange has > been, thought something like this would be a useful quick tool in the > toolbox. > > On 24 February 2016 at 10:35, Claus Ibsen wrote: > >> What kind of logging do you want. >> >> Do you mean that verbose logging you see when there is an exception? >> >> The message history on the exchange is stored as a list of events that >> track the details. But the formatting is done elsewhere. >> >> >> >> On Wed, Feb 24, 2016 at 10:48 AM, James Green >> wrote: >> > Is this possible? >> > >> > We really just want to from().log("${exchange.history}").to() in our >> route. >> > Seems like this should be really easy? >> > >> > Thanks, >> > >> > James >> >> >> >> -- >> Claus Ibsen >> ----------------- >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2