I just did something like that recently for data-dog. My role adds data-dog
agent config entries.
Example usage looks like:
...
roles:
- role: datadog
- role: datadog_monitor
monitors:
mongodb:
instances:
- server: mongodb://localhost:27017/admin
tags:
- mongo_tag_1
- mongo_tag_2
- role: datadog_monitor
monitors:
docker:
init_config:
docker_root: /
socket_timeout: 5
instances:
- url: unix://var/run/docker.sock
include:
- "docker_image:ubuntu"
- "docker_image:ngnx"
exclude:
- ".*"
new_tag_names: true
tag_by_command: false
collect_event: true
collect_container_size: false
collect_images_stats: false
collect_all_metrics: false
tags:
- docker_tag_1
- docker_tag_2
The roles tasks/main.yml selects a template based on the 'monitors' keys:
- fail: msg="Datadog must be configured. Are you missing role datadog?"
when: datadog_etc_confd_dir is not defined
- name: Configure datadog {{ item.monitor }} monitor
template:
src: "conf.d/{{item.key}}.yml.j2"
dest: "{{datadog_etc_confd_dir}}/{{item.key}}.yaml"
owner: "{{datadog_user}}"
notify: restart datadog
with_dict: monitors
These two templates:
# mongodb.yml.j2
# {{ ansible_managed }}
init_config:
{{ item.value | to_nice_yaml }}
# docker.yml.j2
# {{ ansible_managed }}
{% if item.value.init_config is not defined %}
init_config:
{% endif %}
{{ item.value | to_nice_yaml }}
My main goal was to not create complex templates that require the
definition of every data-dog variable. As I have only used this a very
little so far, ymmv. At some point I will create a galaxy submission.
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/81bbfd02-7ad3-479c-8e9f-c57f1d8cde5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
