Observability / o
Observability: peering in Bogotá (BOG) · O-79
xserv-o-6f23e60bd463
Runbook O-79 for Observability in Bogotá (BOG). Marker xserv-o-6f23e60bd463. This page covers peering 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 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.
Observability capacity O-04
Capacity notes for o-04 assume rainy-season power in Miami and festival peaks toward São Paulo. The failure we actually see is a single uplink, not a cartoon partition of the whole continent. Spare ports and a second provider sit on the same runbook.
Observability handoff O-05
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 rollback O-06
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.
- How fast is rollback for o-03?
- The runbook is a command plus a named owner. There is no wait for a weekly change freeze.
- Is transit the default path?
- No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.