Skip to content

Commit f151148

Browse files
authored
Fix tracing doc namespace (#2157)
Problem: The namespace in the tracing doc was inconsistent. Solution: Fix the namespace to be the same throughout the doc.
1 parent 5cde9f2 commit f151148

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

site/content/how-to/monitoring/tracing.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ The first step is to install the collectors. NGINX Gateway Fabric will be config
2424
Create the namespace:
2525

2626
```shell
27-
kubectl create namespace monitoring
27+
kubectl create namespace tracing
2828
```
2929

3030
Download the following files containing the configurations for the collectors:
@@ -37,13 +37,13 @@ Download the following files containing the configurations for the collectors:
3737
Then install them:
3838

3939
```shell
40-
kubectl apply -f otel-collector.yaml -f jaeger.yaml -n monitoring
40+
kubectl apply -f otel-collector.yaml -f jaeger.yaml -n tracing
4141
```
4242

4343
Ensure the Pods are running:
4444

4545
```shell
46-
kubectl -n monitoring get pods
46+
kubectl -n tracing get pods
4747
```
4848

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

5757
```shell
58-
kubectl port-forward -n monitoring svc/jaeger 16686:16686 &
58+
kubectl port-forward -n tracing svc/jaeger 16686:16686 &
5959
```
6060

6161
Visit [http://127.0.0.1:16686](http://127.0.0.1:16686) to view the dashboard.

0 commit comments

Comments
 (0)