[GitHub] camel pull request #1552: Instrument OpenTracing example service2 using the ...

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] camel pull request #1552: Instrument OpenTracing example service2 using the ...

abhinaypm
GitHub user objectiser opened a pull request:

    https://github.com/apache/camel/pull/1552

    Instrument OpenTracing example service2 using the JavaAgent.

    Fix issue with baggage propagating Camel prefixed headers, causing outbound component to throw exception.
    Added agent rule test.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/objectiser/camel opentracing-javaagent

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1552.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 #1552
   
----
commit 117a3ed7895f9eba0055e1e7dce5d4dc93426fd9
Author: Gary Brown <[hidden email]>
Date:   2017-03-07T08:09:39Z

    Instrument OpenTracing example service2 using the JavaAgent.
    Fix issue with baggage propagating Camel prefixed headers, causing outbound component to throw exception.
    Added agent rule test.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] camel pull request #1552: Instrument OpenTracing example service2 using the ...

abhinaypm
Github user objectiser closed the pull request at:

    https://github.com/apache/camel/pull/1552


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---