From 51bcf331977e3817c5b85d2dbdb029267cbdde63 Mon Sep 17 00:00:00 2001 From: Saylor Berman Date: Thu, 20 Jun 2024 08:34:34 -0600 Subject: [PATCH] Fix tracing doc namespace Problem: The namespace in the tracing doc was inconsistent. Solution: Fix the namespace to be the same throughout the doc. --- site/content/how-to/monitoring/tracing.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/site/content/how-to/monitoring/tracing.md b/site/content/how-to/monitoring/tracing.md index e9a395b8cf..bc39f48406 100644 --- a/site/content/how-to/monitoring/tracing.md +++ b/site/content/how-to/monitoring/tracing.md @@ -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.