Multi-Tenant Data Isolation for Government Observability

The isolation challenge in government multi-tenancy

Government organizations often span multiple levels and dozens of business systems, and data from different departments must be strictly isolated. An observability platform carries sensitive operational data such as logs and traces — a cross-tenant leak is a serious incident.

A four-layer isolation model

Observe enforces isolation across four layers:

1. Tenant isolation: a dedicated data namespace per tenant
2. Environment isolation: production, staging and other environments within a tenant
3. Tiered permissions: admin, read-only and restricted roles
4. Quota control: per-tenant limits on log volume, storage and query concurrency

Permission model

• Platform admin: manages tenants, plans and system users
• Tenant admin: manages members, tokens and alerts for the tenant
• Member: read-only or restricted query access

Audit trails

Every sensitive action — login, query, export, token rotation — is recorded in the audit log and can be traced.

A real deployment

A provincial government cloud onboarded logs from 20+ bureaus into a single platform with 20 tenants. Each bureau sees only its own data while the platform team manages everything centrally — cutting cost while satisfying isolation and compliance.