Open haubenr opened 2 years ago
@haubenr: The label(s) area/tracing
cannot be applied, because the repository doesn't have them.
I think I'd like to support jaeger by exporting Otel traces. Jaeger as of 1.35 can directly receive them.
We do need an OpenCensus => OTel exporter - which seems to have existed before but was removed
I prodded the issue here to see if it's unblocked & possible to add back a tracing bridge
https://github.com/open-telemetry/opentelemetry-go/issues/2808
edit looks like the tracing bridge still exists
https://github.com/open-telemetry/opentelemetry-go/tree/main/bridge/opencensus
Note: we want to eventually swap to OTel instead of OpenCensus https://github.com/knative/pkg/issues/855
Sure, sounds like the right move.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen
. Mark the issue as
fresh by adding the comment /remove-lifecycle stale
.
This issue or pull request is stale because it has been open for 90 days with no activity.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
/lifecycle stale
/lifecycle frozen
At the moment knative only supports tracing to Zipkin backends. It would be good to have more options, e.g. supporting Jaeger tracing backends as well (natively, without the need of external converters etc.)
/area API /kind feature
Expected Behavior
knative support Jaeger tracing backends.
Actual Behavior
knative only supports tracing to Zipkin backends.
Steps to Reproduce the Problem
n/a
Additional Info
This issue is a follow-up to these issues that have been closed due to inactivity:
https://github.com/knative/pkg/issues/1076 https://github.com/knative/pkg/issues/1077