modules config (for system) is Linux-specific and not configurable

[dannygoulder]

Hi, thanks for the great module. Really helped me a lot. Just noting that if you use the module on Windows to enable the system module, metricbeat won't start since the load metricset is enabled in the (metricbeat) module config enabled with this (puppet) module. My current workaround is to pass an empty array to the modules param which means that the (enabled by default) system config remains untouched.

In terms of a feature request it'd be really cool if this (puppet) module could use filebeat's capabilities to enable/disable individual modules (i.e. renaming the files) so that we can use the shipped default module files from a given version/platform of metricbeat.

Also in a really ideal world it'd be great to be able to tweak the module configuration in order to enable/disable certain metricsets. I'd particularly like to be able to dynamically configure the number of processes included in a system's metrics depending on how many CPUs it has (and also on the nature of the workload it runs). So exposing a knob to fiddle with the config would be amazing. This may be something I'll have time to work on so I'll just leave this issue here to remind myself.