|
|
| Author |
Message |
Grogman
Cacti User
Joined: 21 Feb 2006
Posts: 52
Location: Spain
|
 Posted: Thu Sep 28, 2006 11:39 am Post subject: Problems drawing PPS maps |
 |
|
Hi,
I'm doing some network maps of the packet per second rate of the interfaces. My problem is that I have to choose the unformatted bwlabel setting in order to get the pps values without getting them multiplied by eight, so I loose the K, M, G, T suffixes, making the map difficult to read when there is a lot of packets in a link...
Is there any trick that I should know in order to solve this?
Thanks!!!  |
|
| Back to top |
|
 |
Howie
Cacti Guru User
Joined: 16 Sep 2004
Posts: 1906
Location: United Kingdom
|
| Posted: Thu Sep 28, 2006 5:15 pm Post subject: Re: Problems drawing PPS maps |
|
|
| Grogman wrote: |
Is there any trick that I should know in order to solve this?
Thanks!!! |
Not at the moment. I'd welcome discussion/suggestions for a not-too-specific way to deal with this problem though.
I have a similar problem in 0.9 where you can have values for NODEs too, and I want to have temperatures (although the same applies for firewall session or DHCP leases too, which other people want).
Is the answer to divide the behaviour up? Maybe you should have to specify the x8 bit (which is currently done as the RRD is read), and then also whether or not to get K,M,G etc. Or possibly it's something like printf() in C, where you can specify the format for the bwlabels.
I don't think that adding more LABELSTYLE options is the best way forward. |
|
| Back to top |
|
|
Grogman
Cacti User
Joined: 21 Feb 2006
Posts: 52
Location: Spain
|
| Posted: Fri Sep 29, 2006 1:57 am Post subject: |
|
|
Hi Howie,
In my opinion, I suggest that the K, M, G setting should be a single, separated setting, as well as the x8 setting, like you wrote in your post. That way, you can modify each setting per separate, which allows much more flexibility, I think 
Thanks for your quick response! |
|
| Back to top |
|
|
niobe
Cacti User
Joined: 10 Mar 2008
Posts: 91
Location: Australia
|
| Posted: Fri Apr 11, 2008 12:41 am Post subject: |
|
|
Was this ever solved? I am having a similar problem now with PPS graphs.
First I get a massive floating point number to several decimal places.
I can scale this numbers myself with TARGET scale:0.001 but this doesn't change the number of numerals shown!
Basically I just want rounding to the nearest whole number.
Second issue is that SCALE does not seem to work with non-percentage values. |
|
| Back to top |
|
|
Howie
Cacti Guru User
Joined: 16 Sep 2004
Posts: 1906
Location: United Kingdom
|
| Posted: Fri Apr 11, 2008 2:31 am Post subject: |
|
|
| niobe wrote: | Was this ever solved? I am having a similar problem now with PPS graphs.
First I get a massive floating point number to several decimal places.
I can scale this numbers myself with TARGET scale:0.001 but this doesn't change the number of numerals shown!
Basically I just want rounding to the nearest whole number.
|
You don't say where you are trying to put this number (bwlabel, node label...), but you should look into IN/OUTBWLABELFORMAT for the first, and for both:
{link:this:bandwidth_in:%d} for an integer value
{link:this:bandwidth_in:%0.2f} for a 2 decimal places values
{link:this:bandwidth_in:%k} for a K,M,G,T suffixed value
{link:this:bandwidth_in:%0.2k} for a K,G,M,T suffixed value with 2 decimal places
(substitute node for link as appropriate)
The '%d' bits are documented in the php manual under sprintf and in the advanced topics section of the weathermap manual.
| Quote: |
Second issue is that SCALE does not seem to work with non-percentage values. |
Why would it? It's for percentages and always has been.
Seriously though, I've been thinking about this for a while, and trying to decide whether I will get even more confused queries if SCALEs were *sometimes* for percentages and sometimes not. Especially since in the typical application, all you really want from weathermap is the number, which you can get right now, and a link that goes red (for example) when the number is "too big". If you set the bandwidth for the link to be just below whatever "too big" is, then you can do that today. Absolute scales will probably turn up in a future version, but not before I've written a page describing how data is processed. |
|
| Back to top |
|
|
niobe
Cacti User
Joined: 10 Mar 2008
Posts: 91
Location: Australia
|
|
| Back to top |
|
|
niobe
Cacti User
Joined: 10 Mar 2008
Posts: 91
Location: Australia
|
| Posted: Fri Apr 11, 2008 2:44 am Post subject: |
|
|
On Scales, I think this would be very nice to define non-percentage scales.
In the case of a packets per second weathermap something like this:
| Code: |
SCALE COREPPS 0 10000 140 0 255 32 32 255
SCALE COREPPS 10000 20000 32 32 255 0 192 255
SCALE COREPPS 20000 30 0 192 255 0 240 0
SCALE COREPPS 30000 40000 0 240 0 240 240 0
SCALE COREPPS 40000 60000 240 240 0 255 192 0
SCALE COREPPS 60000 80000 255 192 0 255 0 0
SCALE COREPPS 80000 100000000 255 0 0 255 0 0 |
I've just made the top-tier very large so it covers extremes.
Something for the wish list anyway!
cheers, |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Register
Profile
Log in to check your private messages
Log in
How did I miss that in the manual??