Hello,
We have multiple remote sites and we have entered them in Distributed monitoring.
When we open the overview, the page loads almost in 1 minute. I have changed the Connect timeout from 10 to 1 second in all sites in Distributed monitoring , but it didn’t help.
Is it normal for Distributed monitoring? if not, how can we speed up the page load?
The component used for transferring monitoring data in a distributed monitoring environment – Livestatus – usually is quite snappy. Problems often are caused by package loss, closed connections, or are MTU related. I’d first check if larger amounts of data can be transferred without problems then check load, interface saturation and connection losses.
Also, could you provide more information like the edition used, the size of the installations and whether dialup connections are involved.
1 Like
We have 56 sites in the Distrubition Monitoring, the mosts sites are located outside the country and almost 10 sites are not reachable. None of them are using dialup connection.
no thats not true.
MTU related? what…
dialup? lol
Enterprise or Raw edition? If enterprise do you use the livestatus proxy?
With livestatus proxy you can get some information about the connections to the single sites.
3 Likes
We are using Raw edition. Does the Raw edition have a livestatus proxy?
No. In such a big distributed setup, i don’t know how good the simple livestatus connection is.
I would definitely recommend to use the enterprise edition with the liveproxy daemon for environments of this size and geogaphic setup.
But at least i would set status hosts for all livestatus connections so that broken connections can be marked down faster and the GUI gets more responsive.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.