[collectd] Bundling plugins (e.g. Plugin:Redis)

[Tom Throckmorton]

On 11/01/2013 04:11 PM, Otis Gospodnetic wrote:
> Hi,
> 
> I'm trying to trace https://collectd.org/wiki/index.php/Plugin:Redis .
>  This plugin doesn't appear to be included in any Collectd package out
> there.  But some others, like mysql or ngingx, seem to be included.
> 
> In case of https://collectd.org/wiki/index.php/Plugin:Redis - I
> actually don't even see where to go to get this plugin, if it's
> available somewhere else, where one would grab it and compile it on
> their own.

The plugin needs to be enabled at build time, by passing --enable-redis
to the configure script, but you'll also need to meet the deps first:

https://collectd.org/wiki/index.php/Plugin:Redis#Dependencies

...so, credis will need to be installed/available for your build.

This is the general pattern for building all of the plugins.

> How come some plugins are not included?

Not all plugins are included in the packages you may be using, because
the depedencies required to build them aren't a standard part of the
build environment and weren't available at build time, or really
*should* be built against a particular version, or require a dependency
that can't be distributed with the source, and therefore *must* be built
by you (the Java and GenericJMX plugins are this way, from what I
recall, because they need to be built against a particular jdk).

In the case where the deps are available to the builder (perhaps a
standard part of the build system, or distro), it's likely the plugins
will be be built.  That's why you get MySQL and nginx plugins, because
those are more generally available.

Make sense?

-tt


> 
> Thanks,
> Otis
> --
> Performance Monitoring * Log Analytics * Search Analytics
> Solr & Elasticsearch Support * http://sematext.com/
> 
> _______________________________________________
> collectd mailing list
> collectd at verplant.org
> http://mailman.verplant.org/listinfo/collectd
>