On 3 February 2011 17:58, Richard Crowley <r...@rcrowley.org> wrote: > On Thursday, February 3, 2011 at 9:53 AM, Adam Gibbins wrote: > > Hi All, > I'm trying to implement a template (for my collectd config) that gives > different results depending on the other modules included on that machine. > I tried to do this by checking for the class tags but it turns out that due > to bug #3049 this is a huge pain and 90% of the time the tags aren't > registered by the time the template is parsed so I don't get my expected > result. > > Use multiple collectd configuration files if you possibly can. Then each > class can manage its own little corner of collectd. Putting > > Include "/etc/collectd.d/*.conf" > > in your main /etc/collectd.conf should make this possible if it isn't by > default. > > Rich >
This could work, although I'd have to modify all my modules that require graphing to call collectd which would be somewhat annoying and would stop the module being so standalone (e.g. we couldn't change monitoring systems so easy). On 3 February 2011 18:14, Brian Gallew <g...@gallew.org> wrote: > Add a fact that's derived from parsing /var/lib/puppet/state/classes.txt. > It will be exactly one run behind, but it will have the complete list of > classes as of the previous run and it's reliable. > I considered this, though as you say the run is going to be delayed which is a little annoying as our puppet runs are only once every half hour. So I'd have to wait an hour for graphing, also seems not as clean as it should be. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
