[
https://issues.apache.org/jira/browse/YUNIKORN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222692#comment-17222692
]
Weihao Zheng commented on YUNIKORN-387:
---------------------------------------
Hi [~wwei], I dig into tempo's documents and find that tempo's distributor uses
the receiver layer from the OpenTelemetry Collector, which accepts trace spans
in Jaeger's format. The Jaeger OpenTelemetry binaries are *almost* backward
compatible with the current Jaeger binaries.
It's okay if we want to use opentelemetry rather than opentracing since
opentelemetry might get more popular in the future. Opentelemtry's trace API
inherits many features from opentracing and extends original interfaces, which
makes it easier to use.
We can choose between Tempo or Jaeger's default backend like elasticsearch by
the tracing components we select in our cluster, which is totally separated
from the tracing logic in yunikorn services. I think we can list these tools in
our documents.
> Use Tracing to Improve YuniKorn's Observability
> -----------------------------------------------
>
> Key: YUNIKORN-387
> URL: https://issues.apache.org/jira/browse/YUNIKORN-387
> Project: Apache YuniKorn
> Issue Type: New Feature
> Components: core - scheduler, shim - kubernetes
> Reporter: Weihao Zheng
> Priority: Major
>
> We can use existing tracing framework to collect tracing information in a
> standardized format for scheduling and resource management. It will improve
> YuniKorn's observability significantly with less work. Here are our design
> ideas:
> [https://docs.google.com/document/d/1MKL9SfTH8Pjw6kBM0vRnyv_ctnxBHAz-iuA7Zbux60E/edit?usp=sharing]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
