Timezone support for viewer and API

[TheVaan]

Hey!

I would appreciate support for timezones for the viewer and the API. Currently, daily active users are grouped for UTC dates. For our product, we need daily active users for UTC+02:00. For our requests for a specific date, we're grouping unique active users between (dd-1)-mm-yyyyT22:00:00 and dd-mm-yyyyT22:00:00. But we also have some use cases where we want to get data for a timespan (a week / a month / ...). It would be awesome telling the api at which timezone we and the api groups the data automatically correct. Currently we need to request each day separate, which results in unnecessary high traffic and long loading times. The difference between daily active users in UTC and UTC+2 is noticeable and has an impact on our decisions. I think someone in timezone with +/-7 has even more impact, because a users in the morning/night are grouped to the wrong "timezone day".

Best regards Jan

[winsmith]

Thanks for the request! I like the idea, and I'll add it to the roadmap, but it might be a while before we get around to it since we're busy with funnels, retention charts and more "smartness".

Note to others: If you think this is super important, comment here so I know we should prioritise it higher <3

Note to self: https://druid.apache.org/docs/latest/querying/granularities.html

[nighthawk]

+1 on this.

We are using TelemetryDeck for an app that is exclusively used in Australia. It would be nice, if it was possible to specify a timezone on the bar/line charts so that for example the "day" granularity looks more like an Australian than a European day.

[johnwilke2]

+1 as well