You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we are currently using Superset and I started to look at using the event flow viz which would fit one of our use cases very nicely. The application that is currently firing in the events is recording the timestamp information as the ISOString() format of date e.g. 2019-06-10T18:10:53.854Z. Looking at this viz it appears to want to have the date provided in the long format that matches the toString() e.g. Mon Jun 10 2019 19:10:53 GMT+0100 (British Summer Time).
Would this be something that you would be interested in me submitted a PR to look to resolve to check for different date formats? Or perhaps you might be able to advise on an alternative approach. I have looked at getting the application that is firing the events changed, but this would affect many downstream systems ;o)
The text was updated successfully, but these errors were encountered:
smitp33
changed the title
Question around date format
Question around date format in Event Flow viz
Jun 10, 2019
Hi, we are currently using Superset and I started to look at using the event flow viz which would fit one of our use cases very nicely. The application that is currently firing in the events is recording the timestamp information as the
ISOString()
format of date e.g.2019-06-10T18:10:53.854Z
. Looking at this viz it appears to want to have the date provided in the long format that matches thetoString()
e.g. Mon Jun 10 2019 19:10:53 GMT+0100 (British Summer Time).Would this be something that you would be interested in me submitted a PR to look to resolve to check for different date formats? Or perhaps you might be able to advise on an alternative approach. I have looked at getting the application that is firing the events changed, but this would affect many downstream systems ;o)
The text was updated successfully, but these errors were encountered: