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

fix(jaeger-documentation): update the documentation to work with the … #5423

Merged
merged 2 commits into from
Sep 13, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 3 additions & 1 deletion docs/distributed-tracing/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,12 @@ Moreover, Quickwit supports natively the [OpenTelemetry gRPC and HTTP (protobuf

## Plug Quickwit to Jaeger

Quickwit implements a gRPC service compatible with Jaeger UI. All you need is to configure Jaeger with a (span) storage type `grpc-plugin` and you will be able to visualize your traces in Jaeger that are stored in any Quickwit's indexes matching the pattern `otel-traces-v0_*`.
Quickwit implements a gRPC service compatible with Jaeger UI. All you need is to configure Jaeger with a (span) storage type `grpc`[^1] and you will be able to visualize your traces in Jaeger that are stored in any Quickwit's indexes matching the pattern `otel-traces-v0_*`.

We made a tutorial on [how to plug Quickwit to Jaeger UI](plug-quickwit-to-jaeger.md) that will guide you through the process.

[^1]: It was `grpc-plugin` until the version 1.58 of Jaeger.

## Send traces to Quickwit

- [Using OTEL collector](send-traces/using-otel-collector.md)
Expand Down
8 changes: 4 additions & 4 deletions docs/distributed-tracing/plug-quickwit-to-jaeger.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,10 +32,10 @@ We can rely on `host.docker.internal` to get the docker bridge ip address, point

```bash
docker run --rm --name jaeger-qw \
-e SPAN_STORAGE_TYPE=grpc-plugin \
-e SPAN_STORAGE_TYPE=grpc \
-e GRPC_STORAGE_SERVER=host.docker.internal:7281 \
-p 16686:16686 \
jaegertracing/jaeger-query:latest
jaegertracing/jaeger-query:1.60
```

### Linux
Expand All @@ -46,10 +46,10 @@ The easiest is probably to use host network mode.

```bash
docker run --rm --name jaeger-qw --network=host \
-e SPAN_STORAGE_TYPE=grpc-plugin \
-e SPAN_STORAGE_TYPE=grpc \
-e GRPC_STORAGE_SERVER=127.0.0.1:7281 \
-p 16686:16686 \
jaegertracing/jaeger-query:latest
jaegertracing/jaeger-query:1.60

```

Expand Down
9 changes: 4 additions & 5 deletions docs/distributed-tracing/send-traces/using-otel-sdk-python.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,10 +36,10 @@ We can rely on `host.docker.internal` to get the docker bridge ip address, point

```bash
docker run --rm --name jaeger-qw \
-e SPAN_STORAGE_TYPE=grpc-plugin \
-e SPAN_STORAGE_TYPE=grpc \
-e GRPC_STORAGE_SERVER=host.docker.internal:7281 \
-p 16686:16686 \
jaegertracing/jaeger-query:latest
jaegertracing/jaeger-query:1.60
```

### Linux
Expand All @@ -50,11 +50,10 @@ The easiest is probably to use host network mode.

```bash
docker run --rm --name jaeger-qw --network=host \
-e SPAN_STORAGE_TYPE=grpc-plugin \
-e SPAN_STORAGE_TYPE=grpc \
-e GRPC_STORAGE_SERVER=127.0.0.1:7281 \
-p 16686:16686 \
jaegertracing/jaeger-query:latest

jaegertracing/jaeger-query:1.60
```

## Run a simple Flask app
Expand Down
4 changes: 2 additions & 2 deletions docs/get-started/tutorials/tutorial-jaeger.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,11 +27,11 @@ services:
command: ["run"]

jaeger-query:
image: jaegertracing/jaeger-query:1.52
image: jaegertracing/jaeger-query:1.60
ports:
- 16686:16686
environment:
- SPAN_STORAGE_TYPE=grpc-plugin
- SPAN_STORAGE_TYPE=grpc
- GRPC_STORAGE_SERVER=quickwit:7281
- GRPC_STORAGE_TLS=false
```
Expand Down
Loading