Read-only users blocked from viewing historical telemetry in data graph widget

Forum
, ,
1

Hello Team,

A customer is facing the below issue with the new data graph widget when high-frequency telemetry meets read-only dashboard users.

Scenario:

Data graph widget default to Real-time / Last Hour for high-frequency data (1 point every 10 seconds, ~360 points). Viewers are operational workers without edit widgets rights.

Issue:

  1. When a read-only user changes the dashboard time frame from “Last Hour” to “Last Day”, the widget hits the 8,640 data point mark and triggers the “Truncated data, change aggregation” error message. Because this message is not localized (e.g., missing German translation) and requires structural widget edits to fix, end-users are completely stuck.
  2. For an admin to adjust this, they have to click Edit Widget, switch to history and set the aggregation and save it. Once done, the widget becomes static not introducing any new data points. To return to live monitoring, they have to repeat the same edit widget steps again to switch back to real-time.
  3. Operational users lack edit rights, they are entirely blocked from viewing older data directly on their main operational dashboards.

Is it possible to allow aggregation adjustments within the real time data view without needing to enter the edit widget menu?

Data graph widget should have a possibility to take a look into a specific time frame and then go back to real time/life data. Now we can only choose the begin of the data in custom , not the end, without choosing historical data.

Please share your suggestions.

2

Without dashboard edit rights, the user should still be able to switch the time mode between live and historical (including setting aggregation). They just aren’t able to store them.

There was also a bug that made it impossible to get rid of the truncated data warning message - this was fixed in a later version.

So my suggestion would be: update to the newest version and see if it works better there.

In addition, I also have some complaints about the historical/live data switching, and communicated those to the Cumulocity team. AFAIK at least some of those issues will be addressed.