History: Observability

Every change to this page, newest first. Expand an entry to see what changed.

← Observability

1. 2 Oct 2026 · +3 −3 lines
   Show changes

   ⋯
     | Field | Why |
     |---|---|
   - | UTC timestamp (to the millisecond), endpoint and method | Support finds your call by time and endpoint. |
   + | UTC timestamp (to the millisecond), endpoint and method | When and where. |
     | HTTP status, `error_code` (or creatives `code`), `reason`, `fields` | What happened. |
     | Latency | Spot slowness before viewers do. |
   - | `Wandura-Request-Id` (rolling out), or `request_id` from an error body | The exact request in Wandura's logs. |
   + | `Wandura-Request-Id`, or `request_id` from an error body | The exact request in Wandura's logs. |
     | `Wandura-Version`, `Wandura-API-Status`, `Retry-After`, `Deprecation`, `Sunset` | Version and lifecycle signals. |
     | Key **prefix** (`wnd_live_ab12cd`), never the key | Which key, safely. |
   ⋯
     | Your `viewer_ref` | Ties Wandura's records to your viewer, without personal data. |
     
   - > **Rolling out.** Every response carries `Wandura-Request-Id`, and every error body `request_id`. Log it on every call.
   + Every response carries `Wandura-Request-Id`, and every JSON error body `request_id`. Log it on every call.
     
     ## Never log {#never-log}
   ⋯

2. 2 Oct 2026 · Page created