[jboss-jira] [JBoss JIRA] (WFLY-12842) MicroProfile Config properties are not taken into account by Jaeger client

[Sultan Zhantemirov (Jira)]

     [ https://issues.jboss.org/browse/WFLY-12842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sultan Zhantemirov updated WFLY-12842:
--------------------------------------
    Attachment: microprofile-config.properties


> MicroProfile Config properties are not taken into account by Jaeger client
> --------------------------------------------------------------------------
>
>                 Key: WFLY-12842
>                 URL: https://issues.jboss.org/browse/WFLY-12842
>             Project: WildFly
>          Issue Type: Bug
>          Components: MP OpenTracing
>    Affects Versions: 18.0.1.Final
>            Reporter: Sultan Zhantemirov
>            Assignee: Emmanuel Hugonnet
>            Priority: Critical
>         Attachments: microprofile-config.properties
>
>
> I am trying to migrate tests from [Thorntail|https://github.com/rhoar-qe/thorntail-test-suite/tree/master/microprofile] test suite, both MP OpenTracing 1.0 and 1.3.
> Let's have a simple Arquillian test with Jaeger containerized in Docker and a WAR-archive with CDI enabled (_beans.xml_) and _META-INF/microprofile-config.properties_ included:
> {noformat}
> jaeger.sampler.param=1
> jaeger.sampler.type=const
> {noformat}
> But it seems that Jaeger instance running in Docker does not take into account the properties defined in WAR's _microprofile-config.properties_ file. It should trace every request to the deployed application but as far as I can see it does not.
> Only manual instantiation and configuration of a Tracer object in @ApplicationScoped service leads to the expected behaviour. With @Inject 'ed tracer there is no success. 
> Regarding that let's imagine a user case: we have a deployment with _ at Traced_ annotated classes/methods, CDI enabled (_beans.xml_) and _META-INF/microprofile-config.properties_ entries for Jaeger configuration. We don't want to modify existing classes (configuring existing tracer instance), we only want trace each REST request.
> From reading the MP Config specs I expect Jaeger using my MP configuration properties (in case none of env or system variables JAEGER_* is set). Does it should work like this or am I missing something? 



--
This message was sent by Atlassian Jira
(v7.13.8#713008)