Skip to content

Update Spaces collector values for setting API keys #1055

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tr0njavolta merged 1 commit into from
Jan 20, 2026
+8 −2
Merged

Update Spaces collector values for setting API keys #1055

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions docs/manuals/spaces/howtos/self-hosted/space-observability.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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.

Expand Down