I was under the impression that the ModulePath was what told it where to load the modules from. That¹s how the documentation for this module makes it sound here:
https://github.com/sebest/collectd-mongodb Scroll down to the Configuration section. I placed the module into /etc/collectd.d/ on my server and that¹s where I have ModulePath pointing to. Just for the sake of it, I tried as you suggested and it didn¹t fix anything. I think that I have the syntax correct for loading the python module as collectd is actually sending mongo related metrics to graphite, the problem is that the metrics are not getting populated correctly and I¹m thinking it has something to do with the error during collectd startup. Thanks, Dan On 2/13/15, 2:19 PM, "Sven Trenkel" <[email protected]> wrote: >On 13.02.2015 20:44, Finn, Dan wrote: > >> Here is the snipet from my collectd.conf file where I enable the plugin: >> >> <Plugin python> >> ModulePath "/etc/collectd.d/" > >Do you have something like > >Include "/etc/collectd.d/*" > >in your collectd config? Because in that case collectd would try to >parse the python script as a config file, which would not work at all. > > >_______________________________________________ >collectd mailing list >[email protected] >http://mailman.verplant.org/listinfo/collectd _______________________________________________ collectd mailing list [email protected] http://mailman.verplant.org/listinfo/collectd
