-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Multi-tenancy aware Time Zones #3509
Comments
Hey @vincent-benbria ! This is indeed a tricky issue. Unfortunately, there's no straightforward solution to that other than to have pre-aggregation per timezone. The reason for it, not all timezones have whole-hour shifts like IST so most of the time hourly granularity doesn't help, and minute one doesn't make sense. Even if we can reduce the timezone set to whole hour shifts daylight saving time becomes the next problem because it's different in each timezone. If you have a lot of tenants most likely you want to consider grouping tenants in one pre-aggregation table and have pre-aggregations per timezone. |
Yes, I do realize that there are half-hour timezones and such. I am asking for the ability to specify which timezones is aggregated PER tenant, so that my Chinese tenant data is not also preaggregated for EST simply because I also have EST tenants. |
@vincent-benbria I see what you're saying. Yeah. It makes sense to have an option to control it on a per-tenant level. I guess it should be done here: Looking forward to contributions here! |
If you are interested in working on this issue, please leave a comment below and we will be happy to assign the issue to you. |
Is your feature request related to a problem? Please describe.
I need to pre-aggregate on each timezone that my clients want reporting on, but I have a diversified group of clients and they are each mostly only interested in their own timezones.
The impact is pretty simple; I have ~500 clients, about 250 are interested in EST, 200 in PST, 5 in BST, 3 in BT (china) and the rest in basically all timezones across Canada/USA. Overall it means that each of my clients need data timezoned to an average of ~1.2 timezones each, but to provide the adequate coverage i need to enable 8 timezones, forcing me to cache 7 times more data than optimal.
Describe the solution you'd like
Introduce a per-tenant timezone list, similar to every other multi-tenancy options
The text was updated successfully, but these errors were encountered: