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

[DOC] Correct Jaeger spelling mistake #4015

Merged
merged 1 commit into from
Aug 28, 2024
+2 −2
Merged

[DOC] Correct Jaeger spelling mistake #4015

Show file tree
Hide file tree
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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/sources/helm-charts/tempo-distributed/get-started-helm-charts/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -352,7 +352,7 @@ Update the `storage` configuration options based upon your requirements:
The Helm chart values in your `custom.yaml` file are configure to use OTLP.
If you are using other receivers, then you need to configure them.

You can configure Tempo can to receive data from OTLP, Jaegar, Zipkin, Kafka, and OpenCensus.
You can configure Tempo can to receive data from OTLP, Jaeger, Zipkin, Kafka, and OpenCensus.
The following example enables OTLP on the distributor. For other options, refer to the [distributor documentation]({{< relref "/docs/tempo/latest/configuration#distributor" >}})

The example used in this procedure has OTLP enabled.
Expand Down
2 changes: 1 addition & 1 deletion docs/sources/tempo/getting-started/instrumentation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ information from a client application with minimal manual instrumentation of the
### Jaeger

{{< admonition type="note" >}}
Jaegar client libraries have been deprecated. For more information, refer to the [Deprecating Jaeger clients article](https://www.jaegertracing.io/docs/1.50/client-libraries/#deprecating-jaeger-clients). Jaegar now recommends using OpenTelemetry SDKs.
Jaeger client libraries have been deprecated. For more information, refer to the [Deprecating Jaeger clients article](https://www.jaegertracing.io/docs/1.50/client-libraries/#deprecating-jaeger-clients). Jaeger now recommends using OpenTelemetry SDKs.
{{% /admonition %}}

- [Jaeger Language Specific Instrumentation](https://www.jaegertracing.io/docs/latest/client-libraries/)
Expand Down
Loading