-
For context, the OpenTracing maintainers are making some people a little miserable by pushing out changes without much compatibility-related prep or, in some cases, follow-through.
On the one hand,…
-
## Feature Request
**Is your feature request related to a problem? Please describe:**
When we enabled opentracing both in our application (e.g.: a java web) and `tidb`, what we finally get is 2 se…
-
[Ingress-NGINX 1.10.0](https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.10.0) has dropped support for OpenTracing and Zipkin, favoring OpenTelemetry instead. The [OpenTelemetry m…
shugg updated
1 month ago
-
Initial version is dependent on opentracing-java version 0.31, but 0.32 (and possibly 0.33 shortly after) will be published with some minor API changes.
-
**Describe the bug**
In some cases, the proxy opentracing span is missing, while the filter processing spans are not.
![no-proxy-span](https://user-images.githubusercontent.com/733217/67796291-0fd…
-
Currently if OpenTelemetry is disabled globally via the ConfigMap option `enable-opentelemetry: "false"` and enabled only in one ingress resource via the annotation `nginx.ingress.kubernetes.io/enable…
-
### Describe the bug
In Opentracing, In consumer interceptor, consumer span context is injected into the header.
https://github.com/opentracing-contrib/java-kafka-client/blob/master/opentracing-kaf…
-
The `opentracing` project is deprecated in favor of `opentelemetry`. Due to ongoing flaws with `opentracing`, we have had difficulty troubleshooting particular bugs that rely on the usage of `opentrac…
-
Follow-up of #3190:
The OpenTracing instrumentation (already using the OpenTelemetry OpenTracingShim) should be replaced with using OpenTelemetry directly, removing all OpenTracing dependencies.
-
For `traceId`