Ping response time report and graphing dispaly incorrect.

Josh,
 See nslookup hobbitping and graph below.
 nslookup ctnhdns1
Server:         147.185.3.141
Address:        147.185.3.141#53

Name:   ctnhdns1.corp.timken.com
Address: 147.185.2.98

hobbitping 147.185.2.98
147.185.2.98 is alive (0.27 ms)


Dennis Riley
 user-9a9b8af7c15c@xymon.invalid


-----Original Message-----
From: Xymon User in Richmond [mailto:user-24d6f8323faa@xymon.invalid]
Sent: Tuesday, August 17, 2010 9:54 AM
To: xymon at xymon.com
Subject: Re: [xymon] Ping response time report and graphing dispaly incorrect.

On Tue, August 17, 2010 09:20, Josh Luthman wrote:

Are you certain they're pinging the same thing?  If you're not using
testip make sure the name is correct and resolving the right IP.

Is it Mu and not ms?

Can we see the graph?

Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX


On Tue, Aug 17, 2010 at 7:18 AM, Riley, Dennis P.
<user-9a9b8af7c15c@xymon.invalid<mailto:user-9a9b8af7c15c@xymon.invalid>> wrote:

Using Xymon 4.2.3 on CentOS 5.2.

When pinging local hosts with sub-ms response times, like 0.25 ms,
the Xymon conn display and graph treat it as 25 ms.

However when pinging remote hosts which have a much larger response
time (much greater than 1 ms), the display and graph seem to
correctly reflect the response time.

Has anyone else seen this?

I see the same thing, both in the graphs and the parenthetical metric at the end of the conn "is alive" line.


xymon-unsubscribe at xymon.com<mailto:xymon-unsubscribe at xymon.com>


This message and any attachments are intended for the individual or
entity named above. If you are not the intended recipient, please
do not forward, copy, print, use or disclose this communication to
others; also please notify the sender by replying to this message,
and then delete it from your system. The Timken Company / The
Timken Corporation