From 2f41605ea662a87fd38428474d65d0b175ccfd88 Mon Sep 17 00:00:00 2001
From: Casey Buto <casey.buto@upbound.io>
Date: Fri, 16 Jan 2026 09:55:05 -0500
Subject: [PATCH] Update Spaces collector values for setting API keys

---
 .../spaces/howtos/self-hosted/space-observability.md   | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/docs/manuals/spaces/howtos/self-hosted/space-observability.md b/docs/manuals/spaces/howtos/self-hosted/space-observability.md
index 7df118df..56bba998 100644
--- a/docs/manuals/spaces/howtos/self-hosted/space-observability.md
+++ b/docs/manuals/spaces/howtos/self-hosted/space-observability.md
@@ -43,12 +43,18 @@ To configure how Upbound exports, review the `spacesCollector` value in your Spa
 ```yaml
 observability:
   spacesCollector:
+    env:
+      - name: API_KEY
+        valueFrom:
+          secretKeyRef:
+            name: my-secret
+            key: api-key
     config:
       exporters:
         otlphttp:
           endpoint: "<your-endpoint>"
           headers:
-            api-key: YOUR_API_KEY
+            api-key: ${env:API_KEY}
       exportPipeline:
         logs:
           - otlphttp
@@ -66,7 +72,7 @@ provider-kubernetes.
 ### Router metrics
 
 The Spaces router component uses Envoy as a reverse proxy and exposes detailed
-metrics about request handling, circuit breakers, and connection pooling. 
+metrics about request handling, circuit breakers, and connection pooling.
 Upbound collects these metrics in your Space after you enable Space-level
 observability.