Time Zone with Pre-Aggregation¶
New Insights framework
We are introducing a new architecture framework for Cognigy Insights, which significantly enhances the application's data processing capacity. This upgraded framework not only improves overall performance but also minimizes loading times for dashboard data. To use this framework, migration is required.
The migration to the new framework is not linked to a specific release. We start with a few dedicated SaaS customers, inform them, and provide assistance for migration. For on-premises customers, the migration guide will be provided soon.
Afterward, we migrate the remaining shared SaaS and dedicated SaaS customers.
In Insights, Time zone settings play a crucial role in presenting time-based data accurately to users based on their geographical location. By selecting the appropriate time zone, you can view data in your local time, which is essential for accurate data analysis and interpretation.
By default, Insights relies on the time zone preferences of your device according to supported time zones.
Supported Time Zones¶
With migrating to the new framework, a significant change was made to the data-fetching process from the database. Before the migration, the system fetched the entire dataset from the database based on the applied filters and time zone, which often resulted in slow queries and timeouts due to the large amount of data being processed.
After migrating to the new framework, Insights introduced pre-aggregation to improve data retrieval performance. Now, Insights groups data by time zones on an hourly basis, enabling quicker queries and on-the-fly data generation. However, the update has reduced the number of supported time zones to optimize efficiency and prevent timeouts.
By default, the (UTC+00:00) UTC time zone supports pre-aggregation.
You can include 2 extra custom time zones (recommended), with a maximum of 5.
If a previously set time zone is not supported, it will be reset to the default time zone or the nearest supported time zone. In the Insights interface, you will see the corresponding warning.
Custom Time Zone¶
The configuration of additional time zones depends on the type of your installation:
Contact your customer success manager to add preferable custom time zones.
If you are using an on-premises environment, you can specify a custom time zone. Note that each time zone selection necessitates a separate set of pre-aggregations, which can increase the system load.
We recommend selecting 2–3 time zones, with UTC included, as the ideal configuration. The maximum allowed limit is 5 time zones, and UTC must always be included in your value.
Before installation or an upgrade, we strongly advise aligning the list of supported time zones with the customer's preferences. To do this, specify CUBEJS_SCHEDULED_REFRESH_TIMEZONES=<time-zone-1>,<time-zone-1>,<time-zone-3> in the values.yaml file. For example, CUBEJS_SCHEDULED_REFRESH_TIMEZONES=UTC,CET,ACST.
Change Time Zone Settings¶
Note
If you decide to set a custom time zone preference, it will be saved in your browser storage. However, keep in mind that if you switch to a different device or browser, you will need to reselect your desired custom time zone preference.
To change time zone preferences, follow these steps:
- Go to Cognigy.AI. interface.
- In the upper-right corner of the Projects page, select User Menu > My Profile.
- In the Preferences section, select time zone from the Select Insights time zone list.
New time zone will be applied to all existing data.
Time Zone Considerations: OData and Insights¶
In the OData feed, all times are consistently presented in UTC format. When comparing time zones from OData to Insights Dashboards, consider this to ensure accurate data interpretation.