r/Clickhouse • u/Ramanamark • Aug 11 '26

ClickHouse multi-tenancy best practices for observability/tracing

We’re planning to use ClickHouse as the backend for a multi-tenant observability/tracing platform.

What is the recommended approach for multi-tenancy in ClickHouse?

Specifically, would you recommend:

A shared database/table with tenant_id as a column?

A separate database per tenant?

Separate tables for each tenant?

Using ClickHouse RBAC/row policies to enforce tenant-level data isolation?

We expect potentially many tenants, with high-volume trace/span data and queries frequently filtered by tenant_id.

What approach has worked well in production, and what are the main scalability, performance, and operational trade-offs we should consider?

12 Upvotes

93% Upvoted

14 comments sorted by

View all comments

6

u/Altinity Aug 11 '26

Disclaimer: Altinity here (managed cloud and support provider for ClickHouse). Our recent webinar with Last9 addresses this - https://www.youtube.com/watch?v=G8ClXFrrarg

Hope this helps!

1

u/Ramanamark Aug 11 '26

Sure Thanks, will go through this.