-
-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Add support for tenants #78
Comments
Hi @mr-karan this is not currently in scope yet, but will surely become an item in the future as we stabilize core features |
Hello @bzed we currently offer multitenancy (as well as full promql support, faster performance, and other features) on https://qryn.cloud and on-prem deployments powered by qryn-go, which will be released once we secure funding the project development short of any sponsors jumping in. |
@lmangani cloud is for various reasons absolutely not an option for us. Could you give us some details about funding and in which state the project is? |
@bzed thanks for asking - we're getting there! We're redesigning qryn-js to be fully based on OTEL collector and once that's one, partitioning is back on the table. Until then Id you'd like to support the project PM me, you can also license and run qryn.cloud on prem w/ full featured partitioning |
Would it be possible to add Multi-Tenancy support similar to https://grafana.com/docs/loki/latest/operations/multi-tenancy/ ?
The way I am thinking for this to work is:
X-Org-ID
header from requestcloki_<tenant>.*
tables (one db/tenant)Loki actually uses a common Index store for all tenants, but chunk store is separated. We could follow the same or IMHO, a separate DB per tenant would provide more isolation.
The text was updated successfully, but these errors were encountered: