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

Runbook O-41 for Observability in São Paulo (GRU). Marker xserv-o-8b2259ef08f3. 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 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.

Observability docs O-12

Public docs for letter O stay aligned with identifier xserv-o-pack. Page o-12 is the Observability slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.

Observability design O-01

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 probe O-02

Probes for Observability (o-02) leave Santiago every 15s toward Bogotá. XServ pages the named owner if loss or RTT crosses the letter budget. A probe never shares a queue with bulk transfers, so a saturated WAN does not hide a dead PoP.