[hobbit] Problem with graph zoom on Network times
White, Bruce
bewhite at fellowes.com
Fri Jan 15 15:23:37 CET 2010
Try a restart of your browser session. I applied the fix and it worked first time with a fresh browser session.
Bruce White
Senior Enterprise Systems Engineer | Phone: 630-671-5169 | Fax: 630-893-1648 | bewhite at fellowes.com | http://www.fellowes.com/
Disclaimer: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc.
-----Original Message-----
From: wiskbroom at hotmail.com [mailto:wiskbroom at hotmail.com]
Sent: Friday, January 15, 2010 8:14 AM
To: hobbit at hswn.dk
Subject: RE: [hobbit] Problem with graph zoom on Network times
I am running 4.3.0.0-beta2 and I too have the same zoom.js, although I see no difference when I modify. Do I have to restart my server? Does this now get entered into the latest version?
.vadim
> Thought I had reported this to the list ;-) For the y-axis, the method
> parseFloat should be used instead of parseInt in zoom.js.
>
> [bb at iris web]$ pwd
> /soft/pub/BB/hobbit/server/web
>
> [bb at iris web]$ diff -u zoom.js.dist zoom.js
> --- zoom.js.dist Fri Mar 27 11:03:32 2009
> +++ zoom.js Wed Apr 8 15:00:06 2009
> @@ -587,8 +587,8 @@
>
> graphStart = parseInt(gUrlObj.getUrlParameterValue("graph_start"));
> graphEnd = parseInt(gUrlObj.getUrlParameterValue("graph_end"));
> - graphTop = parseInt(gUrlObj.getUrlParameterValue("upper"));
> - graphBottom = parseInt(gUrlObj.getUrlParameterValue("lower"));
> + graphTop = parseFloat(gUrlObj.getUrlParameterValue("upper"));
> + graphBottom = parseFloat(gUrlObj.getUrlParameterValue("lower"));
> haveGraphLimits = (gUrlObj.getUrlParameterValue("upper") !=
> undefined) && (gUrlObj.getUrlParameterValue("lower") != undefined);
>
> idxStr = "";
>
>
> Dominique
>
>
> Thomas Eckert wrote:
>> Bruce,
>>
>> I can confirm the same behaviour w/ xymon-4.3.0 snapshot as of 2010-01-08.
>>
>> Running on Gentoo, vanilla-kernel:
>> $ uname -r; epm -q rrdtool
>> 2.6.31.1-install
>> rrdtool-1.3.8
>> Browser: seamonkey 1.1.18 on linux (so most likely not a FF 3.5 bug).
>>
>> Same behaviour in a slightly different setup w/ 4.3.0_beta2 w/ FF 3.5.4.
>>
>> Cheers,
>>
>> Thomas
>>
>> White, Bruce wrote:
>>> Hi all,
>>>
>>>
>>>
>>> Has anyone else seen this issue with their installation of xymon?
>>>
>>>
>>>
>>> ......Bruce
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *Bruce White*
>>>
>>> *From:* White, Bruce [mailto:bewhite at fellowes.com]
>>> *Sent:* Friday, January 08, 2010 2:43 PM
>>> *To:* hobbit at hswn.dk
>>> *Subject:* [hobbit] Problem with graph zoom on Network times
>>>
>>>
>>>
>>> Hi all,
>>>
>>>
>>>
>>> I just noticed an issue with zooming into graphs of my ping time.
>>> When I zoom in, it loses the y-axis value of milliseconds and
>>> presents the data in just seconds. So what was a set of valleys and
>>> peaks becomes a straight line. I did a couple of searches of the
>>> archive, but have not found anyone reporting this issue. I am
>>> running Xymon 4.3.0-0.beta2 on a RedHat AS 5.2 server running 1.2.23
>>> of the rrdtool. I am attaching png files of the graph before (conntime) and after the zoom (connzoom).
>>> It seems to be a problem with any of the graphs where the y-axiz is
>>> in milliseconds (TCP connection Time, bbgen run time, etc.). Has
>>> anyone else seen this issue?
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Bruce
>>>
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
More information about the Xymon
mailing list