Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-7735

Use OpenTelemetry SDK in apicast in place of deprecated jaeger-client-cpp

XMLWordPrintable

    • API CCS Sprint 39 (3Scale), API CCS Sprint 40 (3Scale), API CCS Sprint 42 (3Scale), API CCS Sprint 43 (3Scale), API CCS Sprint 44 (3Scale) 2

      Adds OpenTelemetry distributed tracing support to Apicast.

      Supported propagation types: W3C

      Jaeger has deprecated each clients. From Jaeger doc

      For new applications, we recommend using the OpenTelemetry APIs, SDKs, and instrumentation. Since v1.35, the Jaeger backend can receive trace data from the OpenTelemetry SDKs in their native OpenTelemetry Protocol (OTLP).

      /// dev notes
      Integration with Opentelemetry-cpp-nginx-instrumentation

      Dep on opentelemetry-cpp

      /// release notes

      deprecate jaeger client (based on opentracing) (and drop it, let' say 2 releases?)

          There are no Sub-Tasks for this issue.

              Unassigned Unassigned
              amackenz@redhat.com Andrew Mackenzie
              Darren Fennessy Darren Fennessy
              Matej Dujava Matej Dujava
              Eguzki Astiz Lezaun Eguzki Astiz Lezaun
              Votes:
              1 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 3 days
                  3d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified