Observability: handoff in São Paulo (GRU) · O-77

Runbook O-77 for Observability in São Paulo (GRU). Marker xserv-o-e9bd7388fd9f. This page covers handoff for LATAM operators, not a worldwide average.

Observability: How this letter ties to the rest

Handoff from letter O Observability into the rest of the platform uses the same request IDs as the gateway. Runbook o-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

Observability: A note on cost and transit

Rollback for o-06 is a documented command, not a hope. Transit is billed as backup while Observability prefers peering in Santiago. If cost spikes, the runbook cuts overflow to Bogotá before touching customer prefixes.

Observability: Why it matters on this continent

Design for Observability on letter O starts in São Paulo (GRU). Runbook o-01 keeps a single owner, a written rollback, and a traffic split that can be reversed without a global freeze. Neighbors in Santiago only take overflow after the local pool fails a health window.

Observability cache O-08

Cache rules for Observability on o-08 keep language-correct objects near Miami. São Paulo is a sibling cache, not an origin. TTLs are short enough that a bad asset does not live through a weekend.

Observability headers O-09

Headers for o-09 carry the letter, the region (GRU) and a request id. Observability debugging in São Paulo should not require a packet capture in Santiago first.

Observability timeouts O-10

Timeouts on o-10 are tighter than the WAN RTT to Bogotá. Observability in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

Observability regions O-11

Region names on o-11 match DNS and tickets: Bogotá / BOG, with Miami as the documented pair. Observability dashboards never say “LATAM” as if it were one RTT.