
Sovereign Observability Needs Ownership, Not Just Residency
What is sovereign observability?
Residency is a location. Sovereignty is a control relationship, and observability data now falls squarely inside it.
Key takeaways
-
Logs, traces and metrics routinely contain session tokens, personal data and LLM prompts, so telemetry is sensitive data.
-
Data residency describes where telemetry is stored, while sovereignty describes who holds the keys, the storage and the right to leave.
-
Cost-driven sampling and shorter retention thin out the evidence exactly when NIS2 and DORA reporting deadlines demand more of it.
-
A bring-your-own-cloud model separates operating the platform from owning the data and removes the infrastructure margin built into traditional SaaS pricing.
-
Organizations that own their telemetry can monitor every environment and run AI investigations inside their own perimeter.
Why is telemetry sensitive data?

Telemetry is not exhaust. It is a searchable record of your business and deserves the same classification as the systems it describes.
Is data residency enough for observability?
- SaaS in an EU region: telemetry sits in the vendor's cloud account, the vendor usually holds the keys and operates the platform, infrastructure cost is bundled into the subscription with the vendor's margin, and leaving means exporting and re-ingesting data.
- Self-hosted open source: telemetry, keys and operations all stay with the customer, and so does the engineering effort of running the platform.
- BYOC, vendor-managed: telemetry sits in the customer's cloud account under its own KMS keys, the vendor operates the platform through a control plane, infrastructure is billed at the customer's own cloud rates without a markup, and the data stays in place on exit.
Why does sampling become a compliance problem?
Why did Alan&Eve add Tsuga to its technology partners?
"Managed by Tsuga. Owned by you."
Portability
Pipeline-level redaction
Governance by default
Agents inside the perimeter
A significant cost lever
How do you move toward sovereign observability?

-
Map where telemetry goes today.
List every agent, collector and integration that sends telemetry outside your cloud accounts, including staging and CI. The map shows reach. It does not yet tell you what is sensitive.
-
Classify what telemetry contains.
Sample real log lines, span attributes and agent traces from the busiest services and tag personal data, credentials, customer content and prompts. Classification turns a sovereignty debate into a concrete list. It does not replace fixing logging at the source.
-
Draw the boundary by data class.
Decide which classes must never leave infrastructure you control. Regulated and AI-related telemetry usually stays inside. The boundary does not decide the hosting model on its own.
-
Standardize instrumentation on OpenTelemetry.
Grafana Labs' 2026 survey found OpenTelemetry used for logs at 48% of organizations, with 37% citing freedom to switch vendors as a top reason. Vendor-neutral instrumentation keeps the boundary decision reversible.
-
Redact at the pipeline, before storage.
Mask and route telemetry at ingestion so sensitive fields never reach indexes or dashboards. Pipeline redaction catches what slips through source fixes. It does not clean data already stored elsewhere.
-
Set retention and access per team.
Define retention by data class and purpose, restrict access through SSO and roles, and give AI agents scoped, auditable access. This is where observability becomes governable. Cost ownership still needs per-team attribution.
-
Plan the exit and test it.
Document what you keep, in which format, and how long a switch would take. DORA expects exit strategies for critical ICT services, and the discipline helps everyone else. An untested exit plan is an assumption, not a plan.
Sovereignty that slows incident response will be bypassed
What leaders should measure
- Boundary coverage: the share of telemetry volume that stays inside infrastructure the organization controls.
- Sensitive data leakage: sensitive data findings per week in stored telemetry.
- Evidence readiness: time to produce a complete incident timeline, measured against the NIS2 72-hour window.
- Cost per service: observability spend attributed to owning teams.
- Exit time: estimated time to move platforms without losing retained data.
What to review this week
-
List every destination outside your cloud accounts that receives logs, metrics or traces.
-
Search one day of logs from your three busiest services for tokens, email addresses and authorization headers.
-
Check who holds the encryption keys for stored telemetry and whether you can revoke vendor access yourself.
-
Identify which services or environments are sampled or unmonitored for cost reasons, and who decided.
-
Rehearse NIS2: can your team write a 24-hour early warning from the data you actually retain?
-
Ask your current provider in writing what happens to retained telemetry and dashboards if you leave.
Frequently asked questions
What is the difference between data residency and data sovereignty?
Is BYOC observability more expensive than SaaS?
Does sovereign observability mean we have to self-host?
Do application logs contain personal data under GDPR?
How does NIS2 affect observability?
If telemetry stays in our cloud, is it secure?
Bring your telemetry back inside your boundary
Sources
European Commission: Cloud and AI Development Act (June 3, 2026)
EUR-Lex: Directive (EU) 2022/2555 (NIS2)
EUR-Lex: Regulation (EU) 2022/2554 (DORA)
OWASP: Logging Cheat Sheet
Grafana Labs: 4th Annual Observability Survey (March 18, 2026)