Hi All, Any update on this?
Thanks and Regards On Fri, Jul 10, 2020 at 5:02 PM Rukshan Premathunga <[email protected]> wrote: > Hi All, > > We had an issue with dashboards widgets in past releases, it uses the GMT > timezone to calculate siddhi windows. I found this fixed[1] but looks like > it working for the worker if we use rest API. But in the dashboard runtime > when widgets are loading using WS calls, it still returns time in GMT > timezone. > > I have added the following config in both runtimes. > properties: > aggTimeZone: Asia/Colombo > > here an example: > > *query*: from ApiErrorAnalysisAgg within 0L, 1694194742000L per \"days\" > select AGG_TIMESTAMP group by AGG_TIMESTAMP > > *Worker rest API:* > Long value of AGG_TIMESTAMP: 1594233000000 > GMT: Wednesday, July 8, 2020 6:30:00 PM > Your time zone: Thursday, July 9, 2020 12:00:00 AM (expected behaviour) > > *Dashboard response is taken in the network tab* > Long value of AGG_TIMESTAMP: 1594166400000 > GMT: Wednesday, July 8, 2020 12:00:00 AM > Your time zone: Wednesday, July 8, 2020 5:30:00 AM > > At this time when I check the DB in the day's table, it is persisted > correctly as '1594233000000'. So what could be the reason for this? > > > [1] https://github.com/siddhi-io/siddhi/pull/1637 > > -- > Rukshan C. Premathunga | Associate Technical Lead | WSO2 Inc. > (m) +94711822074 | (w) +94112145345 | Email: [email protected] > GET INTEGRATION AGILE > Integration Agility for Digitally Driven Business > -- Rukshan C. Premathunga | Associate Technical Lead | WSO2 Inc. (m) +94711822074 | (w) +94112145345 | Email: [email protected] GET INTEGRATION AGILE Integration Agility for Digitally Driven Business
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
