Cheshire Cat Computing

Hey hey,

It might be that i'm just to dumb to understand but as i can see on the forums the 95 percentile info should be added somewhere in the graphs (or below the graph). I've searched the forums and am unable to find why it is not showing. Do i need to add something to the router2.cgi file?? Or is it just creating a new graph..

The problem is that i'm not really the programer but a Windows guy who is trying to get this to work..

Thanks for your replies.
Ray

Hi rhandels,

In your routers2.conf you should have 'percentile=yes', if you want to remove it per-target, you can use 'routers2.cgi*Options[]: nopercentile' in your MRTG configurations.

Hope this helps,
Adam

The 95th Percentile information is added as text below the graph, and not as a line or text in the graph image.

The reason for this is historical - the 95th Percentile information is simply not available to router2 at the time of graph generation. To change this would require a major re-write of the code and so it has not been done, although adding 95th Perc line to the graph would be a good feature.

At the moment this is in the wishlist for Routers v3.0

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Hey Guys,

As said i'm quite new and noob to the subject of MRTG and rrd.. I've got it up and running now, also the router2.cgi script and off course i was looking with my eyes closed Thanks for both your info...

And i did see another post that asked for the 95 percentile line in the graph and also the info in the graph itself. The problem is that we are going to measure this for our datacenter and our costumers will be viewing this so we would like it to be as neat as possible But the 3.0 version, do you have any idea when this will be released??

Regards,
Ray

The 3.0 version is a long way off (>1 year) as I have to learn Qooxdoo first... and its a complete rewrite of everything, probably.

If you're using this for multiple customers in a datacentre, take a look at the authentication and authorisation options, you can provide personalised screens for each customer restricted to their own devices (this is what it was designed for)

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Hey Steve,

Curiousity killed the cat, but do you think you're going to stick with perl/js (Qooxdoo) or is this going to be a php/js (Qooxdoo) type re-write?

Also...do you have any sort of roadmap for it? In case there are folks out there that want to contribute code/ideas before the wheels start moving on the 3.0 release.

Thanks,
Adam

This is going to be perl, not PHP (I can't code PHP anyways).

No roadmap yet - I want to get a bit more au-fait with Qooxdoo before making the final decision and plans. Maybe I'll not go with it at all. However it looks like JS-heavy apps with datapumps are the way to go, and something like Qooxdoo will be needed to get a sufficiently spiffy frontend (the old 2000 design is now looking somewhat simple and dated, even with stylesheets)

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11