Dashboard graphs have no data depending on time frame selected

[route-dist]

Problem/Question

Given a graph (app.cpu_utilization in my case) and same time frame selected, the graph that is displayed when viewed in the node - has data, whereas the same graph displayed in the dashboard does not have data.

This tends to happen when selecting custom time frames (select and zoom).

There are graphs that are not affected by it, and there are graphs that are prone to it.

I believe all the graphs in Processes (Apps, Users, Groups) are affected by it.

Example shown below:

app.cpu_utilization in node tab

app.cpu_utilization in custom dashboard tab

app.cpu_utilization in custom dashboard tab with different time frame selected

Relevant docs you followed

• Dashboards tab | Learn Netdata

Environment/Browser/Agent’s version etc

• Browsers
  • Chrome Version 132.0.6834.160
  • Opera One (version: 116.0.5366.71)
  • Firefox 134.0.2
• OS:
  • MacOS 15.2
• Nedata agent:
  • Version: v2.2

What I expected to happen

No missing data in dashboard graphs when using custom time frames

[novykh]

Hello, I can see in the second image that the nodes are selected 0 from 1. I believe you have globally selected a node, but then you added the chart from another node and the global selected node doesn’t have data or doesn’t have the context at all.
This happens because the dashboards are (till now) fluid regarding nodes. So adding a chart it’s not coupled with the pre-selected nodes. So, if you select globally the node that has the context then it will work right away.

This is a feature not a bug, but since it feels like a bug and looks like a bug I decided to give you the best of 2 worlds.

In the next release, this toggle will appear on all the custom dashboards, where you can easily choose between using the preselected nodes (from when you added the chart) or disregard the pre-selection of nodes and behave like today. The value will be saved along with each dashboard and the default behaviour will be to respect the pre-selected nodes of when you added the chart.

Let me share why we did have this behaviour. We have seen it again and again, dashboards becoming obsolete once the nodes associated with them were going stale or offline. But the users still needed the dashboard to work, but only with different selections. This was easily accomplished with how it is today. But you found the edge case, so well done

Please, share if the feature helps you and of course if you find any other issues.

[route-dist]

Hi @novykh ,

Thanks for looking into this.

I think we are heading down the right track. It’s definitely something to do with the node being selected/de-selected. But I think it’s not exactly as how you described.

When graph has data, the node is shown as a named node:

When graph has no data, the node is just represented by an id:

Only the selected node loses its named status, the other non-selected nodes are not affected.

I would like to note again that this only happens when in the zoomed in state. Generally OK in the pre-configured time frames.

[route-dist]

I can now see the “Sync charts with global nodes” and can confirm that toggling it on hasn’t resolved the issue.

[novykh]

Yep, reproduced it and passed it to the backend team to check why they are responding with wrong data.
In my case, using the toggle:

1. I was getting data when the toggle was off and the chart was using the single node selected
2. I was getting NO-data when the toggle was on and it was using all the room nodes. Including the single node in the collection of ids.

Thank you for sharing the issue and details, we will be back asap on this.

[Juan]

hi @route-dist ,

thanks for reporting this issue.

We identified and fixed a bug in our aggregation process that was likely causing your issue.

Could you please verify that the charts are loading properly now?

best,
Juan

[route-dist]

Thanks @Juan ,

It appears that the issue is resolved. Thanks for your prompt response.