You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/05/11 11:12:04 UTC

[jira] [Updated] (CAMEL-11258) Use TracerResolver to obtain Tracer

     [ https://issues.apache.org/jira/browse/CAMEL-11258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-11258:
--------------------------------
    Fix Version/s: 2.19.1
                   2.20.0

> Use TracerResolver to obtain Tracer
> -----------------------------------
>
>                 Key: CAMEL-11258
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11258
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-opentracing
>    Affects Versions: 2.19.0
>            Reporter: Gary Brown
>             Fix For: 2.20.0, 2.19.1
>
>
> Currently tracers can be explicitly created by a camel application, or implicitly located when provided as a dependency via the ServiceLoader based on the Tracer API.
> The OpenTracing community has recently released a new capability designed to help resolve Tracers allowing for more complex configuration and a converter capability to enable tracers to be wrapped to provide additional capabilities (e.g. teeing off logs to another technology).
> Therefore rather than just using the ServiceLoader directly, use the new TracerResolver to provide a more comprehensive approach for obtaining a Tracer.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)