Lexicon
Data residency
Data residency is where data physically lives and gets processed. Why it matters for telemetry full of personal data, and how architectures guarantee it.
Definition
Data residency is the question of where data physically lives: which country or region stores it, and where it is processed along the way. Residency requirements state that certain data must remain within a given geography, whether by law, regulation, or contract.
What it means in observability
Observability has a residency problem it does not always admit to. Telemetry sounds like machine exhaust, but logs routinely carry user identifiers, email addresses, IP addresses, and payloads, personal data in the regulatory sense, and traces map internal systems in detail. Regulations like GDPR and sector rules in finance and healthcare, along with plain customer contracts, increasingly constrain where such data may go. A SaaS observability pipeline that ships every log line to another jurisdiction can turn an engineering convenience into a compliance finding.
How it works in practice
Residency is delivered through architecture. SaaS vendors offer regional instances that store data in a chosen geography, though the processing and support access paths deserve scrutiny beyond the storage marketing. The stronger guarantee is structural: platforms deployed inside your own cloud account inherit residency from the account itself, since data stored in your eu-west-1 is in the EU by construction, not by policy. Pipelines matter too, because routing and redaction decide what crosses borders before storage is even involved.
Where it gets hard
The details hide in the verbs: data stored in region can still be processed, cached, or viewed from elsewhere, and support workflows are a classic leak path. Multi region estates need residency per region without fragmenting observability into disconnected islands. And residency alone is not sovereignty, a distinction that matters as soon as the question shifts from where data sits to whose law reaches it.
Where Tsuga fits
Tsuga inherits residency from your own cloud account: telemetry is ingested, stored, and queried in the regions you run, and it does not leave. Residency becomes a property of the architecture rather than a clause in a contract.
Related terms
- BYOCBYOC, Bring Your Own Cloud, is a deployment model where a vendor's software runs inside the customer's own cloud account, operated by the vendor but living on infrastructure the customer owns.
- Data sovereigntyData sovereignty is the question of whose laws govern your data and who can be compelled to grant access to it.
- Log managementLog management is the practice of collecting, processing, storing, and searching log data at scale: every event record your applications and infrastructure emit, made findable when someone needs it.
- ObservabilityObservability is the ability to understand what is happening inside a system from the data it emits: its logs, metrics, and traces.