You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2011/03/29 11:27:05 UTC

[jira] [Created] (CAMEL-3817) Add breadcrumbId to MDC logging for tracing messages across transports

Add breadcrumbId to MDC logging for tracing messages across transports
----------------------------------------------------------------------

                 Key: CAMEL-3817
                 URL: https://issues.apache.org/jira/browse/CAMEL-3817
             Project: Camel
          Issue Type: Improvement
          Components: camel-core
    Affects Versions: 2.7.0
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
             Fix For: 2.8.0


When Camel consumes messages it should set a new CamelBreadcrumbId header to the message. By default it should set it based on Message ID if not already provided.

Then the MDC logger should expose this id as well as {{breadcrumbId}}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CAMEL-3817) Add breadcrumbId to MDC logging for tracing messages across transports

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012492#comment-13012492 ] 

Claus Ibsen commented on CAMEL-3817:
------------------------------------

Camel will now by default add a header with the key {{breadcrumbId}} containing the message id (to be used as breadcrumb). This ensure that the header is propagated across various transports (the best we can do so far) and can be used to trace the business flow. So you can do JMS->HTTP->JMS and keep the breadcrumbId across.

We chose to use {{breadcrumbId}} as key and not prefix it with Camel to make it more universal, and also Camel will usually filter out any CamelXXX headers by default.

> Add breadcrumbId to MDC logging for tracing messages across transports
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-3817
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3817
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.7.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.8.0
>
>
> When Camel consumes messages it should set a new CamelBreadcrumbId header to the message. By default it should set it based on Message ID if not already provided.
> Then the MDC logger should expose this id as well as {{breadcrumbId}}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CAMEL-3817) Add breadcrumbId to MDC logging for tracing messages across transports

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-3817.
--------------------------------

    Resolution: Fixed

trunk: 1086641.

Update wiki page for MDC logging with more details about this feature.

> Add breadcrumbId to MDC logging for tracing messages across transports
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-3817
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3817
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.7.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.8.0
>
>
> When Camel consumes messages it should set a new CamelBreadcrumbId header to the message. By default it should set it based on Message ID if not already provided.
> Then the MDC logger should expose this id as well as {{breadcrumbId}}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CAMEL-3817) Add breadcrumbId to MDC logging for tracing messages across transports

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012493#comment-13012493 ] 

Claus Ibsen commented on CAMEL-3817:
------------------------------------

There is an option on CamelContext you can use to disable/enable this feature. Its enabled by default.
Similar to the useMDCLogging feature.

> Add breadcrumbId to MDC logging for tracing messages across transports
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-3817
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3817
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.7.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.8.0
>
>
> When Camel consumes messages it should set a new CamelBreadcrumbId header to the message. By default it should set it based on Message ID if not already provided.
> Then the MDC logger should expose this id as well as {{breadcrumbId}}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira