|
|
| Author |
Message |
thomasj
Joined: 27 Mar 2008 Posts: 7
|
Posted: Thu Mar 27, 2008 11:11 am Post subject: [SOLVED] Creating stand alone values CPU,packetloss,latency? |
|
|
Hi!
Been fiddling the last few days with Cacti via a CactiEZ installation and are looking through the different features and plugins.
I have got a map running and i must say im really impressed of this plugin and i am sure this will become permanent in our monitoring setup.
One small thing that i have not found how to do... How do i create standalone values like packetloss, cpu or temp? Is it a Node that i have to use?
I run 0.941
| Description: |
|
| Filesize: |
7.03 KB |
| Viewed: |
3610 Time(s) |

|
|
|
| Back to top |
|
 |
Howie Cacti Guru User
Joined: 16 Sep 2004 Posts: 2036 Location: United Kingdom
|
Posted: Thu Mar 27, 2008 11:22 am Post subject: Re: Creating stand alone values as CPU, packetloss or latenc |
|
|
| thomasj wrote: | Hi!
Been fiddling the last few days with Cacti via a CactiEZ installation and are looking through the different features and plugins.
I have got a map running and i must say im really impressed of this plugin and i am sure this will become permanent in our monitoring setup.
One small thing that i have not found how to do... How do i create standalone values like packetloss, cpu or temp? Is it a Node that i have to use?
I run 0.941 |
Yes, it's just a node that does participate in any links.
Each node can have it's own TARGET, so you can point it to the appropriate rrd file. Then your label is something like
| Code: |
NODE node1a
LABEL CPU {node:this:bandwidth_in}%
|
You can make it a little easier to manage by making it 'follow' another node as you move things around, with:
| Code: |
NODE node1a
POSITION node1 0 30
|
so that will stay 30 pixels below node1, wherever you move node1. You tend to end up with clusters of nodes, with one for the icon and links, and these status nodes around it.
I'll write this up a little better on the website some day soon.
Edit: Actually, it looks like I already did.
|
|
| Back to top |
|
 |
thomasj
Joined: 27 Mar 2008 Posts: 7
|
Posted: Fri Mar 28, 2008 8:24 am Post subject: |
|
|
| Thanks! Now i got some values up!
|
|
| Back to top |
|
 |
laamidd
Joined: 17 Feb 2006 Posts: 48
|
Posted: Tue Apr 01, 2008 8:02 am Post subject: |
|
|
Hi Howie,
We really appreciate your work on this, we love it...we use it now in production in lieu of Compuware's ServerVantage & Vantageview.
I've read and re-read the manual section on special tokens and the page that your link above sends me to several times. I'm still at a loss. I just don't get which special token will get me the values I want.
I have the Advanced Ping Data Source for all of my switches.
How do I get packet loss and latency values to appear seperately under my nodes?
I know the basics, insofar as creating a node that doesn't link to anything...but how do I get a value(s) under that node?
Thanks,
Bob
|
|
| Back to top |
|
 |
laamidd
Joined: 17 Feb 2006 Posts: 48
|
Posted: Tue Apr 01, 2008 2:16 pm Post subject: |
|
|
| Code: | NODE AtlanticCityWC
LABEL Atlantic City WC
POSITION 89 182
TARGET gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds
NODE AtlanticCityWCLatency
LABELFONT 104
POSITION AtlanticCityWC 5 20
LABEL Latency {node:AtlanticCityWC:loss} ms |
This gets me a node with: Latency [UNKNOWN] ms for the label.
From my logs:
04/01/2008 03:09:07 PM - WEATHERMAP: Poller[0] [Map 24] Switches.conf: ReadData: NODE AtlanticCityWC, target: gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds on config line 81 was not recognised as a valid TARGET [WMWARN08]
04/01/2008 03:09:07 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:606] [Map 24] Switches.conf: ReadData: New Target: gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds
If I use bandwidth_in or bandwidth_out instead of loss_ds, I just get a value of 0. It works, and my logs say Target is valid, but I get 0 because I don't think either bandwidth ds is correct to use?
Thanks,
Bob
|
|
| Back to top |
|
 |
Howie Cacti Guru User
Joined: 16 Sep 2004 Posts: 2036 Location: United Kingdom
|
Posted: Tue Apr 01, 2008 2:25 pm Post subject: |
|
|
| laamidd wrote: | | Code: | NODE AtlanticCityWC
LABEL Atlantic City WC
POSITION 89 182
TARGET gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds
NODE AtlanticCityWCLatency
LABELFONT 104
POSITION AtlanticCityWC 5 20
LABEL Latency {node:AtlanticCityWC:loss} ms |
This gets me a node with: Latency [UNKNOWN] ms for the label.
From my logs:
04/01/2008 03:09:07 PM - WEATHERMAP: Poller[0] [Map 24] Switches.conf: ReadData: NODE AtlanticCityWC, target: gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds on config line 81 was not recognised as a valid TARGET [WMWARN08]
04/01/2008 03:09:07 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:606] [Map 24] Switches.conf: ReadData: New Target: gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds
If I use bandwidth_in or bandwidth_out instead of loss_ds, I just get a value of 0. It works, and my logs say Target is valid, but I get 0 because I don't think either bandwidth ds is correct to use?
Thanks,
Bob |
You're on the right track. The DS is right. The problem is that you need *two*
So either
| Code: |
TARGET gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds:loss_ds
|
or
| Code: |
gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds:-
|
would do it.
Possibly your rrd has a latency DS as well, in which case you could fetch that in the 'out' DS.
|
|
| Back to top |
|
 |
laamidd
Joined: 17 Feb 2006 Posts: 48
|
Posted: Wed Apr 02, 2008 1:36 pm Post subject: |
|
|
I wrote my last post hastily. It's packet loss % that I'm trying to get, not latency. I was trying both at one time.
I should have mentioned that I tried:
| Code: |
TARGET gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds:loss_ds
|
Because of needing two ds's.
I just tried:
| Code: |
TARGET gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds:-
|
with no luck:
04/02/2008 11:43:57 AM - WEATHERMAP: Poller[0] [Map 24] Switches.conf: ReadData: NODE AtlanticCityWC, target: gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds:loss_ds on config line 81 had no valid data, according to WeatherMapDataSource_rrd
04/02/2008 11:39:12 AM - WEATHERMAP: Poller[0] [Map 24] Switches.conf: ReadData: NODE AtlanticCityWC, target: gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds:- on config line 81 had no valid data, according to WeatherMapDataSource_rrd
I opened the .rrd with RRD_Editor-Lite and the data source names in there are loss, avg, max, dev, min.
When you say:
| Quote: |
Possibly your rrd has a latency DS as well, in which case you could fetch that in the 'out' DS.
|
What do you mean by the 'out' DS? That would be the second of the two ds's at the end of my Target?
This is the result of the last polling session in the RRD for the advanced ping data template. I don't know if this helps:
RRA AVERAGE:0.5:1:600
DS loss
UTC 1206980400
VALUE 0.00E+00
DS avg
UTC 1206980400
VALUE 8.34E+00
DS max
UTC 1206980400
VALUE 9.81E+00
DS dev
UTC 1206980400
VALUE 5.79E-01
DS min
UTC 1206980400
VALUE 7.87E+00
RRA AVERAGE:0.5:6:700
DS loss
UTC 1205901000
VALUE 0.00E+00
DS avg
UTC 1205901000
VALUE 8.28E+00
DS max
UTC 1205901000
VALUE 1.31E+01
DS dev
UTC 1205901000
VALUE 1.25E+00
DS min
UTC 1205901000
VALUE 7.70E+00
RRA AVERAGE:0.5:24:775
DS loss
UTC 1201586400
VALUE NaN
DS avg
UTC 1201586400
VALUE NaN
DS max
UTC 1201586400
VALUE NaN
DS dev
UTC 1201586400
VALUE NaN
DS min
UTC 1201586400
VALUE NaN
RRA AVERAGE:0.5:288:797
DS loss
UTC 1138320000
VALUE NaN
DS avg
UTC 1138320000
VALUE NaN
DS max
UTC 1138320000
VALUE NaN
DS dev
UTC 1138320000
VALUE NaN
DS min
UTC 1138320000
VALUE NaN
RRA MIN:0.5:1:600
DS loss
UTC 1206980400
VALUE 0.00E+00
DS avg
UTC 1206980400
VALUE 8.34E+00
DS max
UTC 1206980400
VALUE 9.81E+00
DS dev
UTC 1206980400
VALUE 5.79E-01
DS min
UTC 1206980400
VALUE 7.87E+00
RRA MIN:0.5:6:700
DS loss
UTC 1205901000
VALUE 0.00E+00
DS avg
UTC 1205901000
VALUE 7.74E+00
DS max
UTC 1205901000
VALUE 8.20E+00
DS dev
UTC 1205901000
VALUE 1.24E-01
DS min
UTC 1205901000
VALUE 7.65E+00
RRA MIN:0.5:24:775
DS loss
UTC 1201586400
VALUE NaN
DS avg
UTC 1201586400
VALUE NaN
DS max
UTC 1201586400
VALUE NaN
DS dev
UTC 1201586400
VALUE NaN
DS min
UTC 1201586400
VALUE NaN
RRA MIN:0.5:288:797
DS loss
UTC 1138320000
VALUE NaN
DS avg
UTC 1138320000
VALUE NaN
DS max
UTC 1138320000
VALUE NaN
DS dev
UTC 1138320000
VALUE NaN
DS min
UTC 1138320000
VALUE NaN
RRA MAX:0.5:1:600
DS loss
UTC 1206980400
VALUE 0.00E+00
DS avg
UTC 1206980400
VALUE 8.34E+00
DS max
UTC 1206980400
VALUE 9.81E+00
DS dev
UTC 1206980400
VALUE 5.79E-01
DS min
UTC 1206980400
VALUE 7.87E+00
RRA MAX:0.5:6:700
DS loss
UTC 1205901000
VALUE 0.00E+00
DS avg
UTC 1205901000
VALUE 8.97E+00
DS max
UTC 1205901000
VALUE 1.88E+01
DS dev
UTC 1205901000
VALUE 2.83E+00
DS min
UTC 1205901000
VALUE 7.79E+00
RRA MAX:0.5:24:775
DS loss
UTC 1201586400
VALUE NaN
DS avg
UTC 1201586400
VALUE NaN
DS max
UTC 1201586400
VALUE NaN
DS dev
UTC 1201586400
VALUE NaN
DS min
UTC 1201586400
VALUE NaN
RRA MAX:0.5:288:797
DS loss
UTC 1138320000
VALUE NaN
DS avg
UTC 1138320000
VALUE NaN
DS max
UTC 1138320000
VALUE NaN
DS dev
UTC 1138320000
VALUE NaN
DS min
UTC 1138320000
VALUE NaN
RRA LAST:0.5:1:600
DS loss
UTC 1206980400
VALUE 0.00E+00
DS avg
UTC 1206980400
VALUE 8.34E+00
DS max
UTC 1206980400
VALUE 9.81E+00
DS dev
UTC 1206980400
VALUE 5.79E-01
DS min
UTC 1206980400
VALUE 7.87E+00
RRA LAST:0.5:6:700
DS loss
UTC 1205901000
VALUE 0.00E+00
DS avg
UTC 1205901000
VALUE 8.97E+00
DS max
UTC 1205901000
VALUE 1.88E+01
DS dev
UTC 1205901000
VALUE 2.83E+00
DS min
UTC 1205901000
VALUE 7.75E+00
RRA LAST:0.5:24:775
DS loss
UTC 1201586400
VALUE NaN
DS avg
UTC 1201586400
VALUE NaN
DS max
UTC 1201586400
VALUE NaN
DS dev
UTC 1201586400
VALUE NaN
DS min
UTC 1201586400
VALUE NaN
RRA LAST:0.5:288:797
DS loss
UTC 1138320000
VALUE NaN
DS avg
UTC 1138320000
VALUE NaN
DS max
UTC 1138320000
VALUE NaN
DS dev
UTC 1138320000
VALUE NaN
DS min
UTC 1138320000
VALUE NaN
Thanks again,
Bob
|
|
| Back to top |
|
 |
Howie Cacti Guru User
Joined: 16 Sep 2004 Posts: 2036 Location: United Kingdom
|
Posted: Wed Apr 02, 2008 4:00 pm Post subject: |
|
|
| Quote: |
I opened the .rrd with RRD_Editor-Lite and the data source names in there are loss, avg, max, dev, min.
|
OK, so those are the possible names for DS in the TARGET line too. The two DS names on the end are for 'in' and 'out' respectively (because that's where they go for a link, and nodes share a chunk of the same code).
So you'd use something like
| Code: |
TARGET gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss:-
|
or
| Code: |
TARGET gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss:avg
|
Now, once the data is read, it gets put into the 'bandwidth' variables inside weathermap (again, because they were originally done for links). These are always called bandwidth_in and bandwidth_out.
So, in the second TARGET case above, {node:this:bandwidth_in} would produce the loss value and {node:this:bandwidth_out} would produce the average latency value.
After that, you should be back on the path of the article I linked to.
I am in the process of redesigning the website, and once that is done I plan to write up a bunch more of those articles, including a full description with a diagram of where the data goes.
(you should have gotten an error to tell you that 'loss_ds' isn't a valid DS name in your rrd file, and a list of names that are valid - that's a bug. It probably would have been clearer earlier if you had had that )
|
|
| Back to top |
|
 |
laamidd
Joined: 17 Feb 2006 Posts: 48
|
Posted: Thu Apr 03, 2008 2:25 pm Post subject: |
|
|
We've had the day from hell here today. I scrapped my attempt at getting loss and latency numbers (for now) and started from scratch to see if I could get something *simple* going.
So, I have this as my code:
| Code: | NODE AtlanticCityWC
LABEL Atlantic City WC
TARGET rrd:atlantic_city_wc_-_10_6_12_5_traffic_in_434.rrd:traffic_in:traffic_out
POSITION 464 183
NODE AtlanticCityWCIN
LABEL {node:AtlanticCityWC:bandwidth_in}
POSITION AtlanticCityWC 5 20
NODE AtlanticCityOUT
LABEL {node:AtlanticCityWC:bandwidth_out}
POSITION AtlanticCityWC 20 20 |
Should this work?
I get a blacked out node label for AtlanticCityWC and I get two boxes under that with both having a value of 0.
I'm not the sharpest knife in the drawer, but I'm persistent so if I can get something going I'll be happy to document it and provide examples of a config file with corresponding map.
Pic of my map using my config above:
My Logs:
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ProcessString@Weathermap.class.php:468] [Map 26] NJLWD_Field_Switches.conf: ProcessString: replacing {node:AtlanticCityWC:bandwidth_in} with 0
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ProcessString@Weathermap.class.php:460] [Map 26] NJLWD_Field_Switches.conf: ProcessString: used internal property
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ProcessString@Weathermap.class.php:435] [Map 26] NJLWD_Field_Switches.conf: ProcessString: Found appropriate item: WeatherMapNode AtlanticCityWC
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [pre_render@WeatherMapNode.class.php:223] [Map 26] NJLWD_Field_Switches.conf: Node->pre_render: Label Metrics are: 89 x 12 -> 93 x 16
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [NewColourFromPercent@Weathermap.class.php:945] [Map 26] NJLWD_Field_Switches.conf: NCFPC AtlanticCityWC 0_0 0 0 0
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT 90_100 (242,0,36)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT 80_90 (243,19,249)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT 70_80 (102,27,241)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT 60_70 (181,145,255)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT 50_60 (41,18,250)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT 40_50 (87,153,253)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT 30_40 (88,252,252)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT 20_30 (0,159,116)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT 10_20 (3,251,11)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT 1_10 (157,248,0)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT 0_1 (251,234,3)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT 0_0 (0,0,0)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT TIME (255,0,128)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT TITLE (0,0,128)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT BG (255,255,255)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT KEYBG (255,255,255)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT KEYOUTLINE (0,0,0)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [AllocateScaleColours@Weathermap.class.php:2296] [Map 26] NJLWD_Field_Switches.conf: AllocateScaleColours: DEFAULT KEYTEXT (0,0,0)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [DrawMap@Weathermap.class.php:2319] [Map 26] NJLWD_Field_Switches.conf: Start of Map Drawing
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [DrawMap@Weathermap.class.php:2318] [Map 26] NJLWD_Field_Switches.conf: =====================================
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [DrawMap@Weathermap.class.php:2316] [Map 26] NJLWD_Field_Switches.conf: Finished Post-Processing Plugins...
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [run@WeatherMapPostProcessorTest.php:26] [Map 26] NJLWD_Field_Switches.conf: WeatherMapPostProcessorTest Not Enabled
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [DrawMap@Weathermap.class.php:2311] [Map 26] NJLWD_Field_Switches.conf: Running WeatherMapPostProcessorTest->run()
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [DrawMap@Weathermap.class.php:2308] [Map 26] NJLWD_Field_Switches.conf: Running Post-Processing Plugins...
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [weathermap_memory_check@poller-common.php:11] [Map 26] NJLWD_Field_Switches.conf: MEM pre-render 0: memory_get_usage() says 7.4MBytes used. Limit is 256M
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] [Map 26] NJLWD_Field_Switches.conf: About to write image file. If this is the last message in your log, increase memory_limit in php.ini [WMPOLL01]
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [weathermap_memory_check@poller-common.php:11] [Map 26] NJLWD_Field_Switches.conf: MEM postdata 0: memory_get_usage() says 7.4MBytes used. Limit is 256M
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:720] [Map 26] NJLWD_Field_Switches.conf: ------------------------------
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:719] [Map 26] NJLWD_Field_Switches.conf: ReadData Completed.
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:715] [Map 26] NJLWD_Field_Switches.conf: ReadData: Setting 0,0
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:678] [Map 26] NJLWD_Field_Switches.conf: ReadData: No targets for NODE AtlanticCityOUT
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:600] [Map 26] NJLWD_Field_Switches.conf: ReadData for NODE AtlanticCityOUT:
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:599] [Map 26] NJLWD_Field_Switches.conf:
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:715] [Map 26] NJLWD_Field_Switches.conf: ReadData: Setting 0,0
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:678] [Map 26] NJLWD_Field_Switches.conf: ReadData: No targets for NODE AtlanticCityWCIN
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:600] [Map 26] NJLWD_Field_Switches.conf: ReadData for NODE AtlanticCityWCIN:
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:599] [Map 26] NJLWD_Field_Switches.conf:
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:715] [Map 26] NJLWD_Field_Switches.conf: ReadData: Setting 0,0
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:674] [Map 26] NJLWD_Field_Switches.conf: ReadData complete for NODE AtlanticCityWC: 0 0
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] [Map 26] NJLWD_Field_Switches.conf: ReadData: NODE AtlanticCityWC, target: rrd:atlantic_city_wc_-_10_6_12_5_traffic_in_434.rrd:traffic_in:traffic_out on config line 69 had no valid data, according to WeatherMapDataSource_rrd
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@WeatherMapDataSource_rrd.php:383] [Map 26] NJLWD_Field_Switches.conf: RRD ReadData: Returning (NULL,NULL,0)
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] [Map 26] NJLWD_Field_Switches.conf: Target atlantic_city_wc_-_10_6_12_5_traffic_in_434.rrd doesn't exist. Is it a file? [WMRRD06]
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@WeatherMapDataSource_rrd.php:332] [Map 26] NJLWD_Field_Switches.conf: SCALING result by 8
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@WeatherMapDataSource_rrd.php:312] [Map 26] NJLWD_Field_Switches.conf: Special DS names seen (traffic_in and traffic_out).
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:637] [Map 26] NJLWD_Field_Switches.conf: ReadData: Matched for WeatherMapDataSource_rrd. Calling WeatherMapDataSource_rrd->ReadData()
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:606] [Map 26] NJLWD_Field_Switches.conf: ReadData: New Target: rrd:atlantic_city_wc_-_10_6_12_5_traffic_in_434.rrd:traffic_in:traffic_out
04/03/2008 03:18:58 PM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:600] [Map 26] NJLWD_Field_Switches.conf: ReadData for NODE AtlanticCityWC:
Thanks Howie,
Bob
|
|
| Back to top |
|
 |
Howie Cacti Guru User
Joined: 16 Sep 2004 Posts: 2036 Location: United Kingdom
|
Posted: Thu Apr 03, 2008 2:39 pm Post subject: |
|
|
| I don't see what you're trying to do. If you want to show bandwidth between two places, you don't need to do it like this...
|
|
| Back to top |
|
 |
laamidd
Joined: 17 Feb 2006 Posts: 48
|
Posted: Fri Apr 04, 2008 1:49 pm Post subject: |
|
|
I was trying anything yesterday before I left for the day, because I didn't get a chance to work on it all day and I figured I'd try anything at this point.
Sorry if it's a little schizophrenic, but that's the kind of week it's been.
When I was trying to get a loss or latency value from the advanced ping template I tried:
| Code: |
TARGET gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds:loss_ds
and
TARGET gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss_ds:-
and
TARGET gauge:atlantic_city_wc_-_10_6_12_5_loss_159.rrd:loss:avg (which I had the most hope for)
|
with no luck. (fwiw, there isn't a latency ds)
So, I figured I'd try to do something with a built in data template like the "interface traffic" template because from what I read that defaults to "traffic_in, traffic_out".
I've read the mailing list archives, your notes here: http://www.network-weathermap.com/node/87 and the manual again. I *think* I've tried what you've talked about, inpercent and/or outpercent, or bandwidth_in and bandwidth_out.
In the manual, you have:
| Code: |
LABEL {node:fw_a:outvalue} Sessions
|
So I even tried outvalue and invalue. I saw on the mailing list archives where someone else tried invalue and you said that's incorrect, but if it's documented that way you'd change it. So, I gave up on that immediately.
This is what I was able to try today and a note as to the result of each one:
| Code: |
NODE AtlanticCityWC
LABEL Atlantic City WC
TARGET atlantic_city_wc_-_10_6_12_5_traffic_in_434.rrd
POSITION 464 183
NODE AtlanticCityWCIN
#LABEL {node:AtlanticCityWC:traffic_out} gets me "UNKNOWN" & blk label above
#LABEL {node:AtlanticCityWC:traffic_in} gets me "UNKNOWN" & blk label above
#LABEL {node:AtlanticCityWC:bandwidth_out} gets me "0"& blk label above
#LABEL {node:AtlanticCityWC:bandwidth_in} gets me "0" & blk label above
#LABEL {node:AtlanticCityWC:outpercent} gets me "0" with blk label above
#LABEL {node:AtlanticCityWC:inpercent} gets me "0" with blk label above
#LABEL {node:AtlanticCityWC:invalue}gets me "UNKNOWN" & blk label above
#LABEL {node:AtlanticCityWC:outvalue} gets me "traffic_out"
#LABEL {node:AtlanticCityWC:} gets me "UNKNOWN"", label above reads AtlanticCityWC
#LABEL {node:AtlanticCityWC:traffic_in:traffic_out} gets me "0", label above reads AtlanticCityWC.
POSITION AtlanticCityWC 5 20
|
Some excerpts from my logs:
04/04/2008 11:33:33 AM - WEATHERMAP: Poller[0] [Map 26] NJLWD_Field_Switches.conf: Target atlantic_city_wc_-_10_6_12_5_traffic_in_434.rrd doesn't exist. Is it a file? [WMRRD06]
(But the graph keeps getting updated, so my .rrd does exist and it gets populated.)
===================================
04/04/2008 11:33:34 AM - WEATHERMAP: Poller[0] DEBUG: [ProcessString@Weathermap.class.php:468] [Map 26] NJLWD_Field_Switches.conf: ProcessString: replacing {node:AtlanticCityWC:bandwidth_in} with 0
04/04/2008 11:33:33 AM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:715] [Map 26] NJLWD_Field_Switches.conf: ReadData: Setting 0,0
04/04/2008 11:33:33 AM - WEATHERMAP: Poller[0] DEBUG: [ReadData@Weathermap.class.php:674] [Map 26] NJLWD_Field_Switches.conf: ReadData complete for NODE AtlanticCityWC: 0 0
04/04/2008 11:33:33 AM - WEATHERMAP: Poller[0] [Map 26] NJLWD_Field_Switches.conf: ReadData: NODE AtlanticCityWC, target: atlantic_city_wc_-_10_6_12_5_traffic_in_434.rrd on config line 72 had no valid data, according to WeatherMapDataSource_rrd
04/04/2008 11:33:33 AM - WEATHERMAP: Poller[0] DEBUG: [ReadData@WeatherMapDataSource_rrd.php:383] [Map 26] NJLWD_Field_Switches.conf: RRD ReadData: Returning (NULL,NULL,0)
=========================================================================================
04/04/2008 11:28:35 AM - WEATHERMAP: Poller[0] DEBUG: [ProcessString@Weathermap.class.php:468] [Map 26] NJLWD_Field_Switches.conf: ProcessString: replacing {node:AtlanticCityWC:traffic_out} with [UNKNOWN]
=======================================================================================
04/04/2008 01:43:34 PM - WEATHERMAP: Poller[0] DEBUG: [ProcessString@Weathermap.class.php:468] [Map 26] NJLWD_Field_Switches.conf: ProcessString: replacing {node:AtlanticCityWC:inpercent} with 0
I've also tried prefacing the TARGET with rrd:
| Code: |
NODE AtlanticCityWC
LABEL Atlantic City WC
TARGET rrd:atlantic_city_wc_-_10_6_12_5_traffic_in_434.rrd
POSITION 464 183
NODE AtlanticCityWCIN
LABEL {node:AtlanticCityWC:bandwidth_in}
POSITION AtlanticCityWC 5 20
|
but I just get a "0" with a black label above it.
What am I doing wrong?
Thanks,
Bob
|
|
| Back to top |
|
 |
nowplaying
Joined: 09 Apr 2008 Posts: 2
|
Posted: Wed Apr 09, 2008 1:58 pm Post subject: |
|
|
I'm having the exact same problem. The title of this thread says (Solved) but I don't see a resolution here.
According to this thread and the posted How-to, the below code should return the sessions count but it's returning 0 for me.
| Code: | NODE fw1sessions
LABEL {node:this:bandwidth_in} sessions
TARGET gauge:../../../rra/fw1_limelife_local_sessionsalloc_171.rrd:sessionsAlloc |
Any idea what we are doing wrong?
|
|
| Back to top |
|
 |
Howie Cacti Guru User
Joined: 16 Sep 2004 Posts: 2036 Location: United Kingdom
|
Posted: Wed Apr 09, 2008 2:48 pm Post subject: |
|
|
| nowplaying wrote: | I'm having the exact same problem. The title of this thread says (Solved) but I don't see a resolution here.
According to this thread and the posted How-to, the below code should return the sessions count but it's returning 0 for me.
| Code: | NODE fw1sessions
LABEL {node:this:bandwidth_in} sessions
TARGET gauge:../../../rra/fw1_limelife_local_sessionsalloc_171.rrd:sessionsAlloc |
Any idea what we are doing wrong? |
What *you* are doing wrong (laamid isn't the same), is only having one DS name at the end.
laamid, you should be using
| Code: | | TARGET gauge:atlantic_city_wc__10_6_12_5_loss_159.rrd:loss:avg |
(assuming that's what your DSes are called in that RRD)
and any of these would have worked, if you had the node name match in the {} (you could also just use 'this' instead to avoid the problem) - you have AtlanticCityWCIN as the name for the node but you use AtlanticCityWC in the label, which is wrong.
| Code: |
#LABEL {node:AtlanticCityWC:bandwidth_out} gets me "0"& blk label above
#LABEL {node:AtlanticCityWC:bandwidth_in} gets me "0" & blk label above
#LABEL {node:AtlanticCityWC:outpercent} gets me "0" with blk label above
#LABEL {node:AtlanticCityWC:inpercent} gets me "0" with blk label above
|
and I'll fix that mention of outvalue.
|
|
| Back to top |
|
 |
nowplaying
Joined: 09 Apr 2008 Posts: 2
|
Posted: Wed Apr 09, 2008 4:31 pm Post subject: |
|
|
| I figured out the root of my problem. The RRD files were created by root. I forgot to add the apache user to run the cmdphp cronjob. Doh!
|
|
| Back to top |
|
 |
laamidd
Joined: 17 Feb 2006 Posts: 48
|
Posted: Wed Apr 16, 2008 9:41 am Post subject: |
|
|
I'm trying to use this as an example. I can't use {node:this:name} on my AtlanticCityWCIN node, because I want a value for AtlanticCityWC. Is that right?
| Code: |
NODE fw_a
POSITION 100 100
LABEL Firewall A
TARGET fw_a_cpu.rrd:cpu:- fw_a_sessions.rrd:-:sess
NODE fw_a_sessions
POSITION fw_a -30 0
LABEL {node:fw_a:outvalue} Sessions
|
| Code: |
NODE AtlanticCityWC
LABEL Atlantic City WC
TARGET rrd:atlantic_city_wc_-_10_6_12_5_traffic_in_434.rrd:traffic_in:traffic_out
POSITION 464 183
NODE AtlanticCityWCIN
LABEL {node:AtlanticCityWC:bandwidth_in} bandwidth in
POSITION AtlanticCityWC 5 20
NODE AtlanticCityWCOUT
LABEL {node:AtlanticCityWC:bandwidth_out} bandwidth out
POSITION AtlanticCityWC 20 20
|
Should that show two "boxes" one with an in value, one with an out value under the node Atlantic City WC on the map?
In your second node, you use this:
| Code: |
LABEL {node:fw_a:outvalue} Sessions
|
which points to the first node...is that right?
So, I tried this:
| Code: |
{node:AtlanticCityWC:bandwidth_out}
|
To point to my first node.
I'll try using {node:this:name} on the second and third node and it should work?
Everything else is ok?
Thanks,
Bob
|
|
| Back to top |
|
 |
|
Powered by phpBB © 2001, 2005 phpBB Group
|
|