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 tracing doc namespace #2157

Merged
merged 1 commit into from
Jun 20, 2024
Merged

Fix tracing doc namespace #2157

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
8 changes: 4 additions & 4 deletions site/content/how-to/monitoring/tracing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ The first step is to install the collectors. NGINX Gateway Fabric will be config
Create the namespace:

```shell
kubectl create namespace monitoring
kubectl create namespace tracing
```

Download the following files containing the configurations for the collectors:
Expand All @@ -37,13 +37,13 @@ Download the following files containing the configurations for the collectors:
Then install them:

```shell
kubectl apply -f otel-collector.yaml -f jaeger.yaml -n monitoring
kubectl apply -f otel-collector.yaml -f jaeger.yaml -n tracing
```

Ensure the Pods are running:

```shell
kubectl -n monitoring get pods
kubectl -n tracing get pods
```

```text
Expand All @@ -55,7 +55,7 @@ otel-collector-f786b7dfd-h2x9l 1/1 Running 0 9s
Once running, you can access the Jaeger dashboard by using port-forwarding in the background:

```shell
kubectl port-forward -n monitoring svc/jaeger 16686:16686 &
kubectl port-forward -n tracing svc/jaeger 16686:16686 &
```

Visit [http://127.0.0.1:16686](http://127.0.0.1:16686) to view the dashboard.
Expand Down
Loading