Well, one (possible) problem is that rrdtool (used to store perf data) expects
to receive values at least once in a given interval ("heartbeat"):
> heartbeat defines the maximum number of seconds that may pass
> between two updates of this data source before the value of the
> data source is assumed to be *UNKNOWN*.
>
(rrdcreate manpage)
You can see the heartbeat of a RRD archive with rrdinfo:
Find the RRD archive for the data source that does not work (they are unter
zenoss/perf/Devices/<Devicename>).
Run (after putting zenoss/bin into your PATH)
rrdinfo <RRD file>
and look for "minimal_heartbeat". If it is e.g. 20, then if there is not a
value at least every 20 seconds, rrdtool does not store any values it receives
-> no graph.
This is often a problem if values arrive very infrequently (as in your case).
Use rrdtune to increase the heartbeat value (see manpage), that might help.
------------------------
Sebastian Leske
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=10177#10177
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
