[
https://issues.apache.org/jira/browse/CAMEL-11645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136986#comment-16136986
]
ASF GitHub Bot commented on CAMEL-11645:
----------------------------------------
GitHub user objectiser opened a pull request:
https://github.com/apache/camel/pull/1898
CAMEL-11645 - Add pattern exclusion mechanism similar to the one prov…
…ided by the camel-zipkin component
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/objectiser/camel CAMEL-11645
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1898.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1898
----
commit f2236340ccab64533203d12d886b5cbd08d28113
Author: Gary Brown <g...@brownuk.com>
Date: 2017-08-22T15:58:17Z
CAMEL-11645 - Add pattern exclusion mechanism similar to the one provided
by the camel-zipkin component
----
> Add possibility to filter routes which will report spans
> --------------------------------------------------------
>
> Key: CAMEL-11645
> URL: https://issues.apache.org/jira/browse/CAMEL-11645
> Project: Camel
> Issue Type: New Feature
> Components: camel-opentracing
> Affects Versions: 2.19.1
> Reporter: Radek Mensik
>
> Currently all routes are traced with spans.
> It would be nice to somehow filter which routes will be spanned.
> First step could be that some concrete endpoints will report span, for
> example only those used for REST communication.
> As I had checked Decorators, which are used, modification of method boolean
> newSpan() which will reflect configuration could help us to filter at least
> which endpoint types will be spanning.
> For example RestletSpanDecorator would return true, but all others false.
> Best solution would be similar as is in camel-zipkin.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
