Observability / o

Observability: design in São Paulo (GRU) · O-49

xserv-o-93b130aa011a

Runbook O-49 for Observability in São Paulo (GRU). Marker xserv-o-93b130aa011a. This page covers design for LATAM operators, not a worldwide average.

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: How XServ runs it day to day

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.

Observability: What operators should measure

Policy for Observability is versioned as o-03. Operators measure error rate, p95 from Bogotá, and time-to-rollback — not a worldwide average. Changes land in Bogotá first, then Miami, with a hold if either region regresses.

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.

Observability policy O-03

Policy for Observability is versioned as o-03. Operators measure error rate, p95 from Bogotá, and time-to-rollback — not a worldwide average. Changes land in Bogotá first, then Miami, with a hold if either region regresses.

Does Observability on letter O share fate with other letters?
The control plane is shared. Data-plane queues for Observability stay isolated, so incident o-01 cannot drain neighbor letters.
Where is Observability measured first?
From Santiago (SCL) toward Bogotá. A global average is not an SLO for letter O.