Multi-region strategy

When you need it

• Push latency from remote regions is critical (>200ms agent → ingest)
• Compliance — data residency requires storage in a specific geography
• The data volume exceeds single-VM capacity (>20 TB raw)

What to choose

Per-region selector in the UI (simpler)

The user picks a region in the sidebar before viewing. Data is not aggregated across regions.

• Pro: a simple implementation, predictable performance
• Con: a "single pane of glass" is impossible

Server-side federation (harder, will be added later)

The API fans out to all relevant regions and merges on the server.

• Pro: a unified UX
• Con: PromQL aggregation semantics across regions are non-trivial (you cannot just concat matrix-result series with identical labels)