The issue I am having is that in cacti, under monitored devices, the avgerage latency is in the triple digits for ALL devices. Anyone know what would cause this and what things I need to check in cacti to correct this? These devices should not be in the triple digits. An avg (ms) would be in the range of 120 to 500.77 ms for most devices.
Any help is appreciated.
cacti version: 0.8.7g
plugin 2.8
poller type: cactid v
webserver: apache/2.2.13
my sql: 5.0.86
RRDT: 1.2.30
all running on Linux 2.6.xxxxxxx server
monitored devices have a high latency (triple digits)
Moderators: Developers, Moderators
-
- Posts: 6
- Joined: Wed May 02, 2012 5:45 pm
- gandalf
- Developer
- Posts: 22383
- Joined: Thu Dec 02, 2004 2:46 am
- Location: Muenster, Germany
- Contact:
Re: monitored devices have a high latency (triple digits)
So that's triple digit. And what's the problem?lbaskball45 wrote: avgerage latency is in the triple digits for ALL devices.
An avg (ms) would be in the range of 120 to 500.77 ms for most devices.
R.
-
- Posts: 6
- Joined: Wed May 02, 2012 5:45 pm
Re: monitored devices have a high latency (triple digits)
Basically I have the same issue as this person did back in 2005 and his question was never answered.
http://forums.cacti.net/viewtopic.php?f ... 57#p230157
The response time is in triple digits and they should not be. If I ping from Linux CLI its under 50ms usually. Why is it in cacti it constantly changes from 50 to triple digits? Is it the way its designed? I am guessing the numbers are correct in both methods?
http://forums.cacti.net/viewtopic.php?f ... 57#p230157
The response time is in triple digits and they should not be. If I ping from Linux CLI its under 50ms usually. Why is it in cacti it constantly changes from 50 to triple digits? Is it the way its designed? I am guessing the numbers are correct in both methods?
- gandalf
- Developer
- Posts: 22383
- Joined: Thu Dec 02, 2004 2:46 am
- Location: Muenster, Germany
- Contact:
Re: monitored devices have a high latency (triple digits)
<personal opinion>
IMHO, it does not make oo much sense to rely on anything called "rtt", at least when it comes to using ICMP. First, there are many different ways to perform pings (ICMP, TCP, UDP, using different options and ports). And second, there are devices that slow down such wanted traffic and as such, data will be plainly wrong
</personal opinion>
I your case, it is important to know the method you configued for pinging.
As I already stated above, I personally do not put too many CPU cycles of my brain into this data, sorry, but that's it
R.
IMHO, it does not make oo much sense to rely on anything called "rtt", at least when it comes to using ICMP. First, there are many different ways to perform pings (ICMP, TCP, UDP, using different options and ports). And second, there are devices that slow down such wanted traffic and as such, data will be plainly wrong
</personal opinion>
I your case, it is important to know the method you configued for pinging.
As I already stated above, I personally do not put too many CPU cycles of my brain into this data, sorry, but that's it
R.
Who is online
Users browsing this forum: No registered users and 2 guests