You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Weiwei Yang (Jira)" <ji...@apache.org> on 2020/12/18 04:45:00 UTC
[jira] [Issue Comment Deleted] (YUNIKORN-387) Use Tracing to
Improve YuniKorn's Observability
[ https://issues.apache.org/jira/browse/YUNIKORN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weiwei Yang updated YUNIKORN-387:
---------------------------------
Comment: was deleted
(was: [~Weihao Zheng] We need a doc task as well, to get this well documented. Our doc repo is: https://github.com/apache/incubator-yunikorn-site/
Please open a JIRA to track this as well, 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
> Assignee: 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-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org