Merge pull request #431 from viccuad/tracing-metrics

chore: Update tracing & metrics
kubewarden · Jul 29, 2024 · e324a58 · e324a58
2 parents b865f77 + 95ad718
commit e324a58
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/docs/howtos/telemetry/20-tracing-qs.md b/docs/howtos/telemetry/20-tracing-qs.md
@@ -328,3 +328,7 @@ as there is a new service `kubewarden-policy-server` listed in the UI:
 ![Jaeger dashboard](/img/jaeger-ui-home.png "The dashboard of Jaeger")
 
 The Jaeger collector is properly receiving the traces generated by our PolicyServer.
+
+To access the Jaeger UI, you can create an ingress or use
+`kubectl -n jaeger port-forward service/my-open-telemetry-query 16686`
+then go to [localhost:16686](localhost:16686).
diff --git a/docs/howtos/telemetry/30-metrics-qs.md b/docs/howtos/telemetry/30-metrics-qs.md
@@ -58,6 +58,7 @@ This way, the Prometheus Operator can inspect which Kubernetes Endpoints are tie
 Let's create the two ServiceMonitors named `kubewarden-controller` and `kubewarden-policy-server` using the following manifests:
 
 ```yaml
+kubectl apply -f - <<EOF
 apiVersion: monitoring.coreos.com/v1
 kind: ServiceMonitor
 metadata:
@@ -89,6 +90,7 @@ spec:
   selector:
     matchLabels:
       app: kubewarden-policy-server-default
+EOF
 ```
 
 ## Install Kubewarden