Dashboard panels not loading

[Koja]

Thanks for confirming. What OS is the NLS server?

Code: Select all

NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

EDIT: I gave the NLS server two more CPU cores and two more gigabytes of RAM, but this had no effect on dashboards' performance.

[cdienger]

Do you have other dashboards using the same panel types? Are they showing the same behavior if so?

I'd like to get the output of the network section of the dev tools. See attached screenshot for steps to export it.

Please also provide a profile from the system. It can be gathered under Admin > System > System Status > Download System Profile or from the command line with:

/usr/local/nagioslogserver/scripts/profile.sh

This will create /tmp/system-profile.tar.gz.

Note that this file can be very large and may not be able to be uploaded due to its size. This is usually due to the logs in the Logstash and/or Elasticseach directories found in it. If it is too large, please open the profile, extract these directories/files and send them separately.

[Koja]

Do you have other dashboards using the same panel types? Are they showing the same behavior if so?

Yes, the issue was also happening with a couple of other dashboards.

As I previously said, I added some more resources for the NLS virtual machine. But now, to my surprise, when I logged on to NLS and opened every single dashboard - the panels load immediately! I tested this with Firefox, Chrome, Edge-dev and they all work great!

I also tested the same browsers with my colleague's machine (Windows version 1803) and they also work great! Previously, this issue was also apparent on his machine.

So, to me it seems that adding a couple of cores and two gigs of RAM to NLS and a reboot did the trick. What do you think?

[cdienger]

Resources could definitely cause this. Is it up to 10Gigs of memory now? I'm a little surprised, but it all depends on the amount of data it has to search through and how quickly it can turn through and return it.