[
https://issues.apache.org/jira/browse/YUNIKORN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222464#comment-17222464
]
Weiwei Yang edited comment on YUNIKORN-387 at 10/29/20, 4:15 AM:
-----------------------------------------------------------------
Just found this:
https://grafana.com/blog/2020/10/27/announcing-grafana-tempo-a-massively-scalable-distributed-tracing-system/
Might worth to look at as these lines stand out:
# Tempo's receiver layer, wire format, and storage format are all based
directly on standards and code established by OpenTelemetry.
# Tempo is designed to be a robust trace id lookup store whose only dependency
is object storage (GCS/S3)
was (Author: wwei):
Just found this:
https://grafana.com/blog/2020/10/27/announcing-grafana-tempo-a-massively-scalable-distributed-tracing-system/
Might worse to look at as these lines stand out:
# Tempo's receiver layer, wire format, and storage format are all based
directly on standards and code established by OpenTelemetry.
# Tempo is designed to be a robust trace id lookup store whose only dependency
is object storage (GCS/S3)
> 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]
