Hi,
I tried it and it really threw an exception. The problém was, that directive base in graphite.conf is expected to end with a slash. I was missing it. I think that it cause problém only when used with port number.
[graphiteweb] base=http://IP:80
should be [graphiteweb] base=http://IP:80/
Maybe it would be nice feature to sanitize these configuration variables so it would not be so sensitive about trailing slashes.
Thanks for your effort, this problém is solved.
Brgds
Mat -----Original Message----- From: Morten Brekkevold [mailto:morten.brekkevold@uninett.no] Sent: Thursday, April 03, 2014 10:23 AM To: JABUREK Martin Cc: nav-users@uninett.no Subject: Re: Graphite on other machine
On Wed, 2 Apr 2014 12:30:26 +0000 "Martin.Jaburek@cah.cz" Martin.Jaburek@cah.cz wrote:
- since then it does not connect graphite server at all - when I click
on Port Metrics -> some interface, I just got an error - Error loading image. I have done even some code crawling and found an actual requested link: /ipdevinfo/g/port/1/Octets/?timeframe=day
But I wasn't able to trace it any further. I expect, that NAV actually should proxy this request to graphite (thing which is broken). I'm no expert in python so I got lost there.
Yes, the link above should produce a redirect to a Graphite render proxy within NAV.
I hope this can help you pin down the problem.
I would want you to visit the abovementioned link with your browser to see what you get.
-- Morten Brekkevold UNINETT