I'm looking at extending the gmetad.conf format, while still making sure
that it can read the existing config files.
There are two particular lines that interest me:
RRAs "RRA:AVERAGE:0.5:1:244" "RRA:AVERAGE:0.5:24:244"
"RRA:AVERAGE:0.5:168:244" "RRA:AVERAGE:0.5:672:244" \
"RRA:AVERAGE:0.5:5760:374"
data_source "my cluster" [polling interval] address1:port addreses2:port ...
My goal is to allow different sets of RRAs for different sources, while
making sure the existing file format remains valid.
A couple of ideas I've had:
a) allow the RRAs line to be repeated - the most recent version will be
applied to all subsequent data sources
b) a new option, RRAs_for_source, e.g.
RRAs_for_source "my cluster" "RRA:MAX:0.5:1:244" "RRA:MAX:0.5:24:244"
c) define templates:
RRAs_template tmpl1 "RRA:MAX:0.5:1:244" "RRA:MAX:0.5:24:244"
and invoke the template `tmpl1' using an @ or some other special symbol,
which is optional:
data_source "my cluster" [...@tmpl1] [polling interval] address1:port
addreses2:port ...
or
data_source "my cluster" [...@rras=tmpl1] [polling interval] address1:port
addreses2:port ...
d) regex based filename matching:
RRAs_template tmpl1 "RRA:MAX:0.5:100:240" "RRA:MAX:0.5:240:30"
RRAs_template_match tmpl1 ".*/cpu_num.rrd" ".*/swap_total.rrd"
e) call an external script for RRD creation, and pass it the source
name, metric name, etc:
RRD_create_script "/usr/local/bin/create-my-rrd"
Any preferences for this? Anyone facing a similar requirement?
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Ganglia-general mailing list
Ganglia-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-general
