Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distributed tracing should be supported #8092

Closed
hzpfly opened this issue Jun 21, 2019 · 5 comments
Closed

Distributed tracing should be supported #8092

hzpfly opened this issue Jun 21, 2019 · 5 comments
Assignees
Labels
area/API candidate/2.4.0 kind/requirement New feature or idea on top of harbor

Comments

@hzpfly
Copy link

hzpfly commented Jun 21, 2019

What can we help you?

Can we add Distributed tracing feature to harbor?

Distributed tracing

Distributed tracing, also called distributed request tracing, is a method used to profile and monitor applications, especially those built using a microservices architecture. Distributed tracing helps pinpoint where failures occur and what causes poor performance.

OpenTracing

OpenTracing is comprised of an API specification, frameworks and libraries that have implemented the specification, and documentation for the project. OpenTracing allows developers to add instrumentation to their application code using APIs that do not lock them into any one particular product or vendor.

CNCF Jaeger

Jaeger \ˈyā-gər\ is a distributed tracing system, originally open sourced by Uber Technologies. It provides distributed context propagation, distributed transaction monitoring, root cause analysis, service dependency analysis, and performance / latency optimization. Built with OpenTracing support from inception, Jaeger includes OpenTracing client libraries in several languages, including Java, Go, Python, Node.js, C++ and C#. It is a Cloud Native Computing Foundation member project.

References:

  1. What is tracing
@wy65701436 wy65701436 added the kind/requirement New feature or idea on top of harbor label Jun 24, 2019
@steven-zou
Copy link
Contributor

@hzpfly

Thank you for raising the requirement to Habor. We have already known your requirement and put it into our backlog. Let's see if we can plan it in the future. Please keep tuned.

@xaleeks xaleeks self-assigned this Jul 26, 2019
@finkr
Copy link

finkr commented Dec 27, 2019

For the record (and googlers), there was two competing standards (OpenCensus and OpenTracing) which are now merged as opentelemetry.io

@tianon
Copy link
Member

tianon commented Sep 22, 2021

For any folks looking to follow along, this has an official proposal over in goharbor/community#171.

@lindhe
Copy link

lindhe commented Oct 29, 2021

Was this not closed with #15314?

@github-actions
Copy link

github-actions bot commented Jul 7, 2022

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

@github-actions github-actions bot added Stale and removed Stale labels Jul 7, 2022
@chlins chlins closed this as completed Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/API candidate/2.4.0 kind/requirement New feature or idea on top of harbor
Projects
None yet
Development

No branches or pull requests

9 participants