External Data Source dynamic Path Name

[shygh]

Hi i'm new to cacti,

iam using cacti in combination with collectd.

collectd is a deamon which locally collects data like cpu utilisation and stores them into .rrd files.

cacti displayes these files, this works fine, so far.

unfortunately adding the external .rrd files is a little bit inconvenient.

for example cpu collectd stores various files like : cpu-idle.rrd cpu-user.rrd cpu-interrupt.rrd etc. for EACH core.
so on systems with 8 or more cores there a many files (and this is for cpu only, in other areas its similar).

so adding these files takes a lot of time - it would be nice if i have to do this only once... is this possible?

when iam adding a external rrd to cacti i had to told him the path, for instance /rrd/host1/cpu0-idle.rrd etc.

adding the same file for another host i had to put in /rrd/host2/cpu0-idle.rrd

so i have round about 80 hosts - so this eats a lot of time.

MY QUESTION IS:

is there a way to define a host template once, and paths are added dynamically like : /rrd/|host_name|/cpu0-idle.rrd (<- i tried this, won't work) ?

this would be nice !

thanks and pls excuse my bad english (is it bad? i think so)

[BSOD2600]

is there a way to define a host template once, and paths are added dynamically like : /rrd/|host_name|/cpu0-idle.rrd (<- i tried this, won't work) ?

Nope.

While you've found that one can use externally updated rrd files with cacti, it is NOT the recommended way to do things. It will be painful getting it all set up.

[shygh]

gnarf, do you know a cacti compatible sollution??

[shygh]

collectd is able to open a unix socket, so the cacti server theoretically can ask the daemon for values via script.

i don't think that such a script is around here, isnt it?

[BSOD2600]

Possibly, search the script forum. If nothing there, then read in the documentation site how you can go about creating one for cacti.