Page Comparison

...

Getting Started

Background information regarding this subject is available in our Official documentation

Basics

Check the OMD <SITENAME> performance graphs of the affected

...

Network analyze

To see how long the map really needs, we recommend using the network analyzer of your internet browser: Enable Checkmk profilingprofiling#NetworkAnalyzewiththeinternetbrowser.

Debugging with Livestatus

Enable the debug log

How to collect troubleshooting data for various issue types#LivestatusProxy

Debug with the lq queries

Detect long-running lq query.

Do you see any:

• bigger lq query
• a log query
• a periodical message

...

Livestatus queries#Livestatusqueriesovernetwork

One example

Infrastructure

The map

This is a dynamic map with my remote site as a backend. I created and accessed the map via the central site.

Image Modified

The Debugging

This approach is only if you're running a distributed setup. So, in this case, you can run that command on the central site.

...

The whole logfile: lq_nagvis.txt

What I noticed in the logfile

• A significant amount of lq "GET downtimes" commands during the map reload

• If I count the "GET downtimes" lines, there are 4836

  Code Block
  language bash theme RDark
  OMD[mysite]:~$ cat /tmp/lq_nagvis.txt |grep "GET downtimes" |wc -l 4836

  
  

• All the other commands look small and reasonable.

Further debugging

I noticed a lot of "GET downtimes" from the log. Whenever I reload the map, my central site sends thousands of commands via livestatus. 

When I check my Checkmk site, I set several host downtimes. This could explain why my central site collects all Downtimes before nagvis shows the map.

Image Modified

The Workaround

1. Remove all downtimes. The map will open faster
   
   
2. Access the map directly via the remote site/local site
   
   

Related Articles

...