[
https://issues.apache.org/jira/browse/YUNIKORN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189877#comment-17189877
]
Weiwei Yang edited comment on YUNIKORN-387 at 9/3/20, 6:47 AM:
---------------------------------------------------------------
I had a chat with [~wilfreds], and also [~Weihao Zheng], and [~Tao Yang]. Here
is a summary of what we have discussed:
* I think it makes sense to make this on-demand (or at least add some
sampling). Otherwise, it could be overloading the tracing system. Maybe we can
add some annotation for pods to trigger the tracing?
* We agreed that not include the REST API part in the design. Instead, core and
the shim can simply send traces separately. This will simplify the design.
* [~Tao Yang] mentioned that the [OpenTracing|https://opentracing.io/] API
might be merged into [OpenTelemetry|https://opentelemetry.io/] in the near
future, so it makes sense to introduce the abstraction layer and make
OpenTracing is just one implementation.
[~Weihao Zheng], could you pls update the design doc based on our discussion so
folks can review it again? Thanks
was (Author: wwei):
I had a chat with [~wilfreds], and also [~Weihao Zheng], and [~Tao Yang]. Here
is a summary of what we have discussed:
* I think it makes sense to make this on-demand (or at least add some
sampling). Otherwise, it could be overloading the tracing system. Maybe we can
add some annotation for pods to trigger the tracing?
* We agreed that not include the REST API part in the design. Instead, core and
the shim can simply send traces separately. This will simplify the design.
* [~Tao Yang] mentioned that the [OpenTracing|https://opentracing.io/] API
might be merged into [OpenTelemetry|https://opentelemetry.io/] in the near
future, so it makes sense to introduce the abstraction layer and make
OpenTracing is just one implementation.
[~Weihao Zheng], could you pls update the design doc based on our discussion so
folks can review it again? Thanks
> 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: [email protected]
For additional commands, e-mail: [email protected]
