camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-11258) Use TracerResolver to obtain Tracer
Date Thu, 11 May 2017 11:15:05 GMT

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

Claus Ibsen resolved CAMEL-11258.
---------------------------------
    Resolution: Fixed
      Assignee: Gary Brown

Gary I granted your user karma to self assign tickets

> 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
>            Assignee: Gary Brown
>             Fix For: 2.19.1, 2.20.0
>
>
> 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)

Mime
View raw message