Observability: probes in Santiago (SCL) · O-74

Runbook O-74 for Observability in Santiago (SCL). Marker xserv-o-b380e8c75361. This page covers probes for LATAM operators, not a worldwide average.

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: Failure modes we actually see

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 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.