ansible-beats
ansible-beats copied to clipboard
elastic
Added support for Beats modules
Implemented support for managing Beats modules. For the case of default configuration, it assumes the corresponding module to be present inside the modules.d directory.
Basic usage
Enabling modules with custom configuration
Enable the nginx module with custom configuration:
beat_modules:
nginx:
config:
access:
enabled: true
var.paths: ["/var/log/nginx/access.log", "/var/log/nginx/*/access.log"]
error:
enabled: true
var.paths: ["/var/log/nginx/error.log", "/var/log/nginx/*/error.log"]
Enabling modules with default configuration
Enable the system and redis modules with default configuration:
beat_modules:
system:
redis:
Disabling modules
Disable the rabbitmq module:
beat_modules:
rabbitmq:
enabled: false
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?
![cla-checker-service[bot] avatar](https://avatars.githubusercontent.com/u/6764390?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @stoffus, Thanks for opening this PR. We'll try to review it soon. Please be patient.
It's working in Production Environment. (test with my own fork)
Is it possible to review this change and add this feature ?
This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. To track this PR (even if closed), please open a corresponding issue if one does not already exist.
@ladislavmacoun please don't let this go stale. What needs to happen next?
@ladislavmacoun please don't let this go stale. What needs to happen next?
Sorry @devmills, I can't help you with this since I am not a member of elastic team, also we have moved from the official beat role and not using this anymore.
