-
Task
-
Resolution: Done
-
Critical
-
None
-
5
-
False
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Yes
-
+
-
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?)
- is related to
-
THREESCALE-9548 Review Prerequisites of Configuring APIcast to use OpenTracing
-
- Defining
-
- relates to
-
THREESCALE-9539 APIcast Opentelemetry instrumentation using the APIcast Operator
-
- To Ship To On-Prem
-
- mentioned on
1.
|
Bring upstream sources to downstream |
|
Closed | |
Unassigned |
2.
|
Build openresty-opentelemetry RPM package |
|
Closed | |
Unassigned |
3.
|
Bind apicast configuration to opentelemetry config |
|
Closed | |
Unassigned |
4.
|
Investigate Cachito integration in RPM builds |
|
Closed | |
Unassigned |
5.
|
Build openresty RPM locally |
|
Closed | |
Unassigned |
6.
|
PoC build opentelemetry dynamic library as docker stage |
|
Closed | |
Unassigned |
7.
|
Build Apicast brew build with Opentelemetry |
|
Closed | |
Unassigned |
8.
|
openresty RPM: enable s390x |
|
Closed | |
Unassigned |
9.
|
Release openresty rpm with opentelemetry support |
|
Closed | |
Unassigned |