Graphing issues

[bwells]

bwells [http://community.zenoss.org/people/bwells] created the discussion

"Graphing issues"

To view the discussion, visit: http://community.zenoss.org/message/74102#74102

--------------------------------------------------------------
I am running Zenoss Core 4.2.0 and am having some issues with graphing.  I have local monitoring templates set up for Accedians to graph 2-way delay, 1-way delay variation, and packet loss.  I am having issues with 2-way delay graphing correctly.
Each Accedian is set up to measure performance statistics to each other Accedian.  When I test each data source/OID it reports the correct value (that the Accedian is reporting), but some of them aren't graphing these values.
Here are 2 examples (from the same device) using the rrd tool:

This one appears to be working fine.  When I test the datasource/oid it reports 53538 (~53ms), which appears to be graphing accurately.

rrdtool fetch DNVR-PTL-TwoWayD_DNVR-PTL-TwoWayD.rrd AVERAGE

1374595500: 5.3536586667e+04
1374595800: 5.3537793333e+04
1374596100: 5.3538000000e+04
1374596400: 5.3538000000e+04
1374596700: 5.3538000000e+04
1374597000: 5.3539586667e+04
1374597300: 5.3540793333e+04
1374597600: 5.3536750000e+04
1374597900: 5.3534300000e+04
1374598200: 5.3537400000e+04
1374598500: 5.3534600000e+04
1374598800: 5.3534000000e+04
1374599100: 5.3538250000e+04
1374599400: 5.3535600000e+04
1374599700: 5.3536700000e+04
1374600000: 5.3538700000e+04
1374600300: 5.3537300000e+04
1374600600: 5.3539550000e+04
1374600900: 5.3540850000e+04
1374601200: 5.3538450000e+04
1374601500: -nan

when i test the datasource/oid for this one it reports the correct value of 12468 (~12ms).  It is not graphing the correct values and I am not sure how the following values are being calculated...

rrdtool fetch DNVR-SLC-TwoWayD_DNVR-SLC-TwoWayD.rrd AVERAGE

1374595500: 0.0000000000e+00
1374595800: 1.0577777778e-02
1374596100: 1.1357802395e+07
1374596400: 2.9587552476e+06
1374596700: 3.3333333333e-03
1374597000: 3.3333333333e-03
1374597300: 6.2954848842e-03
1374597600: 1.2169073995e+07
1374597900: 1.4316557649e+07
1374598200: 2.1474836532e+06
1374598500: 2.6500000000e-02
1374598800: 1.2169073996e+07
1374599100: 1.4316557634e+07
1374599400: 2.1474836507e+06
1374599700: 1.2169074004e+07
1374600000: 2.1474836588e+06
1374600300: 1.2169074002e+07
1374600600: 2.1474836498e+06
1374600900: 9.0000000000e-03
1374601200: 4.3333333333e-03
1374601500: -nan

If anyone could provide some help, it would be much appreciated.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74102#74102]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[bwells]

bwells [http://community.zenoss.org/people/bwells] created the discussion

"Re: Graphing issues"

To view the discussion, visit: http://community.zenoss.org/message/74103#74103

--------------------------------------------------------------
I have also found the following in the rrd.journal file located in /opt/zenoss/var/rrd_journals

Devices that are graphing correctly are getting updates then writing the file:

update /opt/zenoss/perf/Devices/10.7.108.241/HNSN-DNVR-TwoWayD_HNSN-DNVR-TwoWayD.rrd 1374638107:605
wrote /opt/zenoss/perf/Devices/10.7.108.241/HNSN-DNVR-TwoWayD_HNSN-DNVR-TwoWayD.rrd
update /opt/zenoss/perf/Devices/10.7.108.241/HNSN-PLY-TwoWayD_HNSN-PLY-TwoWayD.rrd 1374638107:38734
wrote /opt/zenoss/perf/Devices/10.7.108.241/HNSN-PLY-TwoWayD_HNSN-PLY-TwoWayD.rrd
update /opt/zenoss/perf/Devices/10.7.108.241/HNSN-PTL-TwoWayD_HNSN-PTL-TwoWayD.rrd 1374638107:34305
wrote /opt/zenoss/perf/Devices/10.7.108.241/HNSN-PTL-TwoWayD_HNSN-PTL-TwoWayD.rrd
update /opt/zenoss/perf/Devices/10.7.108.241/HNSN-SLC-TwoWayD_HNSN-SLC-TwoWayD.rrd 1374638107:11887
wrote /opt/zenoss/perf/Devices/10.7.108.241/HNSN-SLC-TwoWayD_HNSN-SLC-TwoWayD.rrd

On the device that is not graphing correctly it is writing the file, then getting the updates.  The updates show that it is actually getting the correct data, but the files are being written before getting the updates:

wrote /opt/zenoss/perf/Devices/10.7.100.241/DNVR-PLY-TwoWayD_DNVR-PLY-TwoWayD.rrd
wrote /opt/zenoss/perf/Devices/10.7.100.241/DNVR-HNSN-TwoWayD_DNVR-HNSN-TwoWayD.rrd
wrote /opt/zenoss/perf/Devices/10.7.100.241/DNVR-SLC-TwoWayD_DNVR-SLC-TwoWayD.rrd
wrote /opt/zenoss/perf/Devices/10.7.100.241/DNVR-PTL-TwoWayD_DNVR-PTL-TwoWayD.rrd
update /opt/zenoss/perf/Devices/10.7.100.241/DNVR-PLY-TwoWayD_DNVR-PLY-TwoWayD.rrd 1374638063:31466
update /opt/zenoss/perf/Devices/10.7.100.241/DNVR-HNSN-TwoWayD_DNVR-HNSN-TwoWayD.rrd 1374638063:610
update /opt/zenoss/perf/Devices/10.7.100.241/DNVR-PTL-TwoWayD_DNVR-PTL-TwoWayD.rrd 1374638063:53534
update /opt/zenoss/perf/Devices/10.7.100.241/DNVR-SLC-TwoWayD_DNVR-SLC-TwoWayD.rrd 1374638063:12467

Still working on figuring this out...
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74103#74103]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[bwells]

bwells [http://community.zenoss.org/people/bwells] created the discussion

"Re: Graphing issues"

To view the discussion, visit: http://community.zenoss.org/message/74131#74131

--------------------------------------------------------------
Okay.  So I got this working.  I initially set these as counters, but later realized I want gauge.
I changed them to gauge in the gui and some of them worked and some didn't.

In directory:  /opt/zenoss/perf/Devices/xxxx
I found that some still said counter in the rrd file.

# rrdtool info DNVR-PLY-TWDelay_DNVR-PLY-TWDelay.rrd
filename = "DNVR-PLY-TWDelay_DNVR-PLY-TWDelay.rrd"
rrd_version = "0003"
step = 300
last_update = 1374696225
header_size = 1832
ds[ds0].index = 0
ds[ds0].type = "COUNTER"
ds[ds0].minimal_heartbeat = 900
ds[ds0].min = NaN
ds[ds0].max = NaN
ds[ds0].last_ds = "31471.0"

I deleted the graphs/datapoints from the gui and found that sometimes the rrd file would be deleted from the directory above and sometimes the rrd file still existed.  I had to manually remove some files. I then added a new datapoint/graph in the gui (with a new name and set as gauge).  This seemed to clear everything up.
There may have been an easier way to do this, but being somewhat novice I just kind of fumbled through it.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74131#74131]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[jmp242]

jmp242 [http://community.zenoss.org/people/jmp242] created the discussion

"Re: Graphing issues"

To view the discussion, visit: http://community.zenoss.org/message/74124#74124

--------------------------------------------------------------
If you change the graph definition sufficiently you need to delete the RRD file so Zenoss recreates a new one with the new values. I used to think any graph definition change aside from thresholds required a deletion of the RRD file, but in 4.2.4 anyway, some changes like the y values (for example) do not require that. You found it depends on some non documented factors.

--
James Pulver
ZCA Member
CLASSE Computer Group
Cornell University
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74124#74124]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]