Trace keycloak calls

Description

In Quarkus we can log all requests using opentracing feature. However it is not the case about requests made by the authentication mechanism using keycloak. It would be nice to add them in opentracing because keycloak can be a point of failure. Also it may be useful to collect response time to analyze them afterwards.

Implementation ideas quarkus-keycloak-authorization used VertX VertxHttpFacade to make calls. VertX web seems to be also used by rest endpoint. So maybe that we could add TraceId, SpanId into VertxHttpFacade ? (It is a suggestion) by using the same traceId used from the rest call.

Some implementations on how to add trace feature for Vertx web can be found in this project:

        <dependency>
            <groupId>io.opentracing.contrib</groupId>
            <artifactId>opentracing-vertx-web</artifactId>
            <version>1.0.0</version>
        </dependency>

[stuartwdouglas]

I don’t see any problems with this, but obviously things like tokens and other credentials should not be included in the data.

[sberyozkin]

Hi @pedroigor yeah, well, I was again being a bit paranoid here 😃, suggesting that exposing the KC traces to a Quarkus endpoint user is the info which is arguably sensitive - shows the traget address of the OIDC server which is outside of the scope of tracing the application specific calls through the distributed system. That said, if it is configurable (ex, block exposing these traces if needed) then may be it is all right. CC @stuartwdouglas as well