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.

Sign up for GitHub

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

Jump to bottom

fix(distributed-tracing): correct typos and update copy #354

Open
wants to merge 1 commit into
base: release-2.5.0
Choose a base branch
from
Open

fix(distributed-tracing): correct typos and update copy #354

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/administration/distributed-tracing/_index.md
View file
Open in desktop
Expand Up @@ -3,9 +3,9 @@ title: Distributed Tracing
weight: 37
---

Observability is a key feature for operating a service in production and using this data you can identify abnormal statuses and make informed decisions to fix issues when an error occurs. The distributed tracing is key element of observability in modern application. Harbor can provide distributed tracing data for operators and administrator to know the current running status and to help troubleshooting. Harbor expose tracing data using the [OpenTelemetry](https://opentelemetry.io/) sdk, you can eazily export traces via Otel protocol which can comsumed by [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/) then expose to almost the on-prem or cloud trace backend. Because of the popularity [Jaeger](https://www.jaegertracing.io), Harbor also can expose tracing data to Jaeger backend directly.
Observability is a key feature for operating a service in production, allowing you to identify abnormal statuses and make informed decisions to fix issues when an error occurs. Distributed tracing is key element of observability in modern application. Harbor can provide distributed tracing data for operators and administrators to understand the current running status and to help with troubleshooting. Harbor expose tracing data using the [OpenTelemetry](https://opentelemetry.io/) SDK so you can easily export traces via the otel protocol, which can be consumed by the [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/) for export to many on-prem or cloud trace backends. Because of the popularity of [Jaeger](https://www.jaegertracing.io), Harbor also can expose tracing data to the Jaeger backend directly.

In harbor v2.4 and later you are able to enable distributed tracing in you Harbor [configuration file](../../install-config/configure-yml-file.md). But we only support one exporter at a time( you can not set bosh or none of them if you enabled tracing). You can set otel as exporter and leveraging OpenTelemetry Collector to retransmit to multiple backend if you want to send data to multiple exporter. And similarly, Jaeger exporter support agent mode and endpoint mode, but only one mode can enabled at a time.
In Harbor v2.4 and later you are able to enable distributed tracing in your Harbor [configuration file](../../install-config/configure-yml-file.md). Only one exporter is supported at a time; if tracing is enabled, you must set one and you cannot set both. If you want to send data to multiple exporters, you can set otel as the exporter and leverage the OpenTelemetry Collector to retransmit to multiple exporters. Similarly, the Jaeger exporter supports agent mode and endpoint mode, but only one mode can enabled at a time.

# Exposed data

Expand Down