Monit/CollectD - Best Approach?

[Andy L]

We use Ansible to install/configure Postgres, Memcached, Redis, Nginx and a bunch of other services.

Now we want to use Ansible to setup monitoring (Monit) and metrics collection (CollectD).

Monit and CollectD each use 'service plugins'.  Plugin configuration can all reside in a single config file, or broken into a master config with separate include files for each plugin.  We could setup monitoring/metrics to operate from a single role, or use separate roles for Monit and CollectD, or embed monitoring/metrics as tasks in each service role.  As we update configurations, we need to account for install dependencies and service restarts.

Does Ansible have a built-in solution for these type of cross-cutting services?  Where can I find examples that show best practice for configuring tools like Monit and CollectD?
 

[Dick Davies]

We're rolling this out now - way I've done it is to make a collectd
role that does universal
checks (CPU, memory etc) and enables the include directory. That roles
defaults/main.yml
also defines things like the path to the include directory,
handlers/main.yml defines a 'bounce collectd'
handler and so on.

Then roles that have collectd plugins they want to use define the
collectd role as a dependency
and template an include file into the right place, notifying the
collectd roles handler as that changes.

> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-proje...@googlegroups.com.
> To post to this group, send email to ansible...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/23a05920-dcaf-47b7-a108-fef644d8eae8%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.