Skip to content

Commit

Permalink
Fix tracing doc namespace (#2157)
Browse files Browse the repository at this point in the history
Problem: The namespace in the tracing doc was inconsistent.

Solution: Fix the namespace to be the same throughout the doc.
sjberman authored Jun 20, 2024
1 parent 5cde9f2 commit f151148
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions site/content/how-to/monitoring/tracing.md
Original file line number Diff line number Diff line change
@@ -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:
@@ -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
@@ -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.

0 comments on commit f151148

Please sign in to comment.