Nagios Support Forum

Yup and thanks.

This instance has one gearman worker. We had 2CPU and 8GB of RAM for the server before. It is now on 4CPU with 16GB of RAM. According to CCM, we have 221 hosts and 4176 services. Not too much. We have another instance with about 1500 hosts and about 24065 service counts that's using 6CPU with 20GB o...

Thanks. Just to put things in context why this is important because a spike that happens in one minute will not show an accurate value over 5 minutes. So in my review, my 1 minute spike at 9:29am will show a cpu load of 40, but looking at the spike on a 5 minute graph, that spike shows up as a 10 at...

So I've noticed some spikes in latency for some of our hosts and rtmax spikes up to 150ms. After investigation, it is actually the Nagios XI server that is causing these "spikes". When checking ping times from other servers, it seems to be quite stable, but at the same time a ping session ...

Looks like this doesn't work. As the scaling is adjusted, but the timing also gets affected. Noticed the graphs with the time difference.

before after

Thanks and understood. I will test this on our test environment first.

I've been looking through the template for the multistack graphs. There are is a line where the interval is set. pointInterval: {$args['increment']}*1000, //time scale, 5mn Could I change this in the mean time to hardcode the interval to 1min? If so, what's the right value here to adjust?

Just noticed that on the newer XI, it is showing intervals of 5 mins. However I think I know what the difference is. If I use graph explorer and use the scalable performance graph, it shows perf data in 1 min intervals. Where as the multistacked performance graphs shows data in 5mins. We use the sta...

I m looking in my dashboard as well as the graph explorer. The service uses a template and I've attached them here. I noticed you were using XI5 and this was on 2014. I had a different test server on XI5 and noticed the default was in fact 1min. even when check intervals are at 5mins. So perhaps it ...

The service details confirms the check intervals...

Service State: Ok
Duration: 6d 19h 28m 9s
Service Stability: Unchanging (stable)
Last Check: 2016-04-18 13:20:00
Next Check: 2016-04-18 13:21:00