Xymon Mailing List Archive search

trending graph generation

3 messages in this thread

list Larry Barber · Thu, 12 May 2011 13:15:38 -0500 ·
I believe I have found a bug when you generate trending graphs for custom
periods. It seems that the display name is used in the command rather than
the "true" name. For instance, if you have a hosts.cfg entry like this:

1.2.3.4 fully.qualified.domain.name    # yadda yadda yadda NAME:display_name

The trends page uses "display_name" when you ask it to generate custom
length graphs. You can hack the URL and replace the display name with the
real name (fully.qualified.display.name above) and everything works fine.

Thanks,
Larry Barber
list Phil Crooker · Fri, 13 May 2011 11:38:14 +1000 ·
Larry Barber  05/13/11 3:46 AM >>>
quoted from Larry Barber
I believe I have found a bug when you generate trending graphs for
custom
periods. It seems that the display name is used in the command rather
than
the "true" name. For instance, if you have a hosts.cfg entry like
this:
1.2.3.4 fully.qualified.domain.name    # yadda yadda yadda
NAME:display_name
The trends page uses "display_name" when you ask it to generate custom
length graphs. You can hack the URL and replace the display name with
the
real name (fully.qualified.display.name above) and everything works
fine.
Thanks,
Larry Barber
So you are saying the graph doesn't display? We use this feature a lot
and don't have a problem seeing the graphs. If you remove the NAME
entry, does it work? Does the problem only happen when the NAME thing is
at the end of the line?
list Phil Crooker · Tue, 17 May 2011 11:23:33 +1000 ·
Hi Larry,

You are going to have to do some troubleshooting. As I said this NAME
directive does work for others, so there may be a bug with xymon or
there may be some odd issue with your installation. There is nothing
obviously wrong, so please, look into your log fies, turn up debugging,
try different things to see if you can work out what is happening. 

Good luck and let us know how you went.

cheers, Phil

On 5/14/2011 at 12:12 AM, in message
<BANLkTiniY+X6p=Dv9nYLi-oLo=user-a4f4cdfbe28a@xymon.invalid>, Larry Barber
<user-6ef9c2864140@xymon.invalid> wrote: 
FYI: I just upgraded to 4.3.3, and the problem still exists.

Thanks,
Larry Barber

On Fri, May 13, 2011 at 8:08 AM, Larry Barber <user-6ef9c2864140@xymon.invalid>
wrote:
I removed the NAME: directive from one of the affected hosts, and
the
trends graphing worked fine after that. Of course, then I had a
screwed up
name showing up on the main page.

Thanks,
Larry Barber


On Thu, May 12, 2011 at 9:44 PM, Phil Crooker
<user-e8e31cd73303@xymon.invalid>wrote:
Well, when you can, why don't you try removing the directive. As I
said,
we don't have a problem and we have about 1/3 of our monitored
hosts
with using NAME.

cheers

Larry Barber  05/13/11 11:25 AM >>>
No the graph doesn't display, you just get a page saying "file not
found" or
something along those lines (I'm not at place where I can check
right
now).
As far as I know it doesn't matter where the NAME directive is on
the
line.
I suspect that if you removed the name directive then everything
would
work
OK.

Thanks,
Larry Barber
quoted from Phil Crooker

On Thu, May 12, 2011 at 8:38 PM, Phil Crooker wrote:
Larry Barber  05/13/11 3:46 AM >>>
I believe I have found a bug when you generate trending graphs
for
custom
periods. It seems that the display name is used in the command
rather
than
the "true" name. For instance, if you have a hosts.cfg entry
like
this:
1.2.3.4 fully.qualified.domain.name    # yadda yadda yadda
NAME:display_name
The trends page uses "display_name" when you ask it to
generate
custom
length graphs. You can hack the URL and replace the display
name
with
the
real name (fully.qualified.display.name above) and everything
works
fine.
Thanks,
Larry Barber
So you are saying the graph doesn't display? We use this feature
a lot
and don't have a problem seeing the graphs. If you remove the
NAME
entry, does it work? Does the problem only happen when the NAME
thing
is
at the end of the line?

--

This message from ORIX Australia might contain confidential
and/or
privileged information. If you are not the intended recipient,
any
use,
disclosure or copying of this message (or of any attachments to
it) is
not authorised.

If you have received this message in error, please notify the
sender
immediately and delete the message and any attachments from your
system. Please inform the sender if you do not wish to receive
future
communications by email.

ORIX handles personal information according to a Privacy Policy
that
is
consistent with the National Privacy Principles. Please let us
know if
you would like a copy. It is also available at
http://www.orix.com.au
.