Observability
This page lists the minimum observability signals you should capture for production support.
Correlation fields (log these)
| Field | Where it comes from |
|---|---|
realm_id | app config |
principal_id | your request context |
billing_account_id | mapping table or token issue response |
Idempotency-Key | your client headers |
X-Request-Id | your request headers (recommended) |
| response envelope | Vluna response |
Hints
Treat hints as machine-readable signals:
- record them in logs
- aggregate counts by hint type
- alert on unexpected spikes (for example,
pricing.not_configured)
Metrics (recommended)
- request rate and latency per endpoint
- error rate by status code and error code
- idempotent replay rate
- rate limit events
- wallet insufficient balance events
Next
- Operational safety: Operational safety