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
Found a subtle and low-priority issue, more of a UI/user-expectation problem with Insight graphs:
On bursty/quiet networks, the "No Data Available" screens show up when there has been no traffic on the interfaces specified for some hours.
Not broken, just misleading, the UI here does not naturally lead a user to understand they can see older data, with the following workarounds:
By selecting an older/larger date range (where there is network traffic recorded), the insight graphs show back up.
By putting traffic across the monitored network interfaces, after some time, (hours?), the graphs show back up.
On quiet/bursty networks, the "No Data Available" message leads users to believe there is something broken with the data, (particularly after searching the net for that error). On regularly busy networks, the insight data always shows the rich data in the UI.
--
Open suggestions for workarounds:
EASY: Perhaps Change the words "No Data Available" to "No Data Available In This Time Range" (implying that the user should fiddle with a larger date range to maybe see some data).
HARD: Change the graph to show empty graphs when there is empty data, and only show the message "No Data Available" when there is something wrong with the data, (corrupted or disabled, etc...). Looks like this could become quite a rabbit hole into re-workng subtle interactions of the UI and the data.
The text was updated successfully, but these errors were encountered:
After skimming codebase for 19.1 future work, pretty sure I don't even see the same base components for this issue, so my request may be a waste of time to address.
With that, core team please feel free to simply close out this ticket if it is not directly relevant to future releases :)
Hi @dotike, The "No Data Available" can still happen, it has been a long time ago since I build this component, but if I remember correctly it was kind of a struggle to display empty graphs with nvd3 here. Changing the title may be a good solution to make it a bit more explicit that the message is related to the timeframe.
@dotike in 19.1 missing data should be presented as zero's due to fad4b3c, we might consider fixing the pie chart at some point in time too, but that's probably not really necessary.
I'm a HUGE fan of the OPNSense Insight tooling, extremely useful to me.
Have seen a great deal of work go into fixing the "No Data Available" issue, e.g.:
https://forum.opnsense.org/index.php?topic=6879.msg30037#msg30037
This is related to, but not the same as, those issues (which are now resolved).
Found a subtle and low-priority issue, more of a UI/user-expectation problem with Insight graphs:
On bursty/quiet networks, the "No Data Available" screens show up when there has been no traffic on the interfaces specified for some hours.
Not broken, just misleading, the UI here does not naturally lead a user to understand they can see older data, with the following workarounds:
On quiet/bursty networks, the "No Data Available" message leads users to believe there is something broken with the data, (particularly after searching the net for that error). On regularly busy networks, the insight data always shows the rich data in the UI.
--
Open suggestions for workarounds:
EASY: Perhaps Change the words "No Data Available" to "No Data Available In This Time Range" (implying that the user should fiddle with a larger date range to maybe see some data).
HARD: Change the graph to show empty graphs when there is empty data, and only show the message "No Data Available" when there is something wrong with the data, (corrupted or disabled, etc...). Looks like this could become quite a rabbit hole into re-workng subtle interactions of the UI and the data.
The text was updated successfully, but these errors were encountered: