Cumulocity IoT Feedback Portal
In using data-point-table widget, when aggregation set to 1day, the "DATE&TIME" field is set to "{date} 09:00:00"
- This value has less information and may be misleading,
it is desirable to show "{date}" (when aggregating for 1 day)
"{date} HH" (when aggregating for 1 hour)
"{date} HH:mm" (when aggregating for 1 minute)
(Current manner of displaying time may give the meaning that the (minimum/maximum) value has measured at 09:00)
- Should this value be set to "{date} 00:00:00" ?
This time(09:00:00) means aggregation was calculated from 09:00:00 to 09:00:00 next day.
In Japan, this behavior is not normal.
With Cumulocity IoT 10.6 and higher, the UI behaviour will be changed and
if daily aggregation is chosen, the time indication will be removed
if hourly aggregation is chosen, the minute and second indication will be removed
if minutely aggregation is chosen, the second indication will be removed
With Cumulocity IoT 10.6 and higher, the UI behaviour will be changed and
if daily aggregation is chosen, the time indication will be removed
if hourly aggregation is chosen, the minute and second indication will be removed
if minutely aggregation is chosen, the second indication will be removed
Thanks again for your feedback!
Many thanks for the good feedback.
The current behaviour of the widget is the following:
The aggregation is done in UTC (server time)
Before displaying the aggregated data, the UI converts the aggregated data into the browser's timezone
Based on your feedback we plan to:
Explain in the documentation, how the aggregation logic works
In the UI
if daily aggregation is chosen, the time indication will be removed
If hourly aggregation is chosen, the minute indication will be removed
If minutely aggregation is chosen, the second indication will be removed
We were discussing your feedback internally and concluded that, the timezone to choose (device time, UTC, browser time) for an aggregation is different from use-case to use-case.
For use-cases that cannot be covered by the generic aggregation logic we recommend customers to persist the aggregated data within Cumulocity IoT using an Apama stream processing rule or Microservice.