Suspend and Resume a Tenant
Suspending a tenant blocks its writes and queries without deleting it. xScaler keeps the existing metric data. Resume the tenant whenever you want the access back.
Use suspension to:
- Temporarily cut off a decommissioned environment
- Block a tenant that is causing runaway series growth
- Pause ingestion during maintenance
Suspend a tenant
From the tenant list:
- Go to Tenants in the sidebar (under Organization).
- Find the tenant you want to suspend.
- Click the ··· (more) menu on the right side of the tenant row.
- The action panel opens on the right. Click Suspend tenant.
- Confirm the action when prompted.
The tenant status changes to Suspended (amber badge). xScaler rejects remote_write requests for this tenant until you resume it.
From the tenant detail page:
- Go to Organization → Tenants → click the tenant name.
- Click the Suspend tenant button in the top-right corner (amber).
- Confirm the action.
Resume a tenant
From the tenant list:
- Go to Tenants in the sidebar (under Organization).
- Find the suspended tenant (filter by Suspended status if needed).
- Click the ··· (more) menu on the right side of the row.
- In the action panel, click Resume tenant (green button).
From the tenant detail page:
- Go to Organization → Tenants → click the tenant name.
- Click Resume tenant in the top-right corner (green).
The tenant status returns to Active and ingestion resumes immediately.
What happens to data during suspension
| During suspension | |
|---|---|
Inbound remote_write | Rejected (HTTP 403) |
| Queries | Blocked |
| Stored metric data | Retained: no data is deleted |
| API tokens | Remain valid: they work again once resumed |
| Series count | Preserved |
Audit trail
The Activity log records every suspension and resumption. The events tenant.suspended and tenant.activated include the timestamp and the user who performed the action.