community.zabbix.zabbix_template – Create/update/delete/dump Zabbix template
Note
This plugin is part of the community.zabbix collection (version 1.5.1).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.zabbix
.
To use it in a playbook, specify: community.zabbix.zabbix_template
.
Synopsis
This module allows you to create, modify, delete and dump Zabbix templates.
Multiple templates can be created or modified at once if passing JSON or XML to module.
Requirements
The below requirements are needed on the host that executes this module.
python >= 2.6
zabbix-api >= 0.5.4
Parameters
Parameter |
Comments |
---|---|
List of template names to be unlinked and cleared from the template. This option is ignored if template is being created for the first time. |
|
Format to use when dumping template with This option is deprecated and will eventually be removed in 2.14. Choices:
|
|
Basic Auth password |
|
Basic Auth login |
|
List of template names to be linked to the template. Templates that are not specified and are linked to the existing template will be only unlinked and not cleared from the template. |
|
Zabbix user password. If not set the environment variable |
|
Zabbix user name. If not set the environment variable |
|
List of user macros to create for the template. Macros that are not specified and are present on the existing template will be replaced. See examples on how to pass macros. |
|
Name of the macro. Must be specified in {$NAME} format. |
|
Value of the macro. |
|
Removes the date field for the exported/dumped template Requires Choices:
|
|
URL of Zabbix server, with protocol (http or https). If not set the environment variable |
|
Required state of the template. On On On The Choices:
|
|
List of host groups to add template to when template is created. Replaces the current host groups the template belongs to if the template is already present. Required when creating a new template with |
|
JSON dump of templates to import. Multiple templates can be imported this way. Mutually exclusive with template_name and template_xml. |
|
Name of Zabbix template. Required when template_json or template_xml are not used. Mutually exclusive with template_json and template_xml. |
|
XML dump of templates to import. Multiple templates can be imported this way. You are advised to pass XML structure matching the structure used by your version of Zabbix server. Custom XML structure can be imported as long as it is valid, but may not yield consistent idempotent results on subsequent runs. Mutually exclusive with template_name and template_json. |
|
The timeout of API request (seconds). Default: 10 |
|
If set to False, SSL certificates will not be validated. This should only be used on personally controlled sites using self-signed certificates. If not set the environment variable Choices:
|
Notes
Note
If you use login_password=zabbix, the word “zabbix” is replaced by “****” in all module output, because login_password uses
no_log
. See this FAQ for more information.
Examples
---
- name: Create a new Zabbix template linked to groups, macros and templates
local_action:
module: community.zabbix.zabbix_template
server_url: http://127.0.0.1
login_user: username
login_password: password
template_name: ExampleHost
template_groups:
- Role
- Role2
link_templates:
- Example template1
- Example template2
macros:
- macro: '{$EXAMPLE_MACRO1}'
value: 30000
- macro: '{$EXAMPLE_MACRO2}'
value: 3
- macro: '{$EXAMPLE_MACRO3}'
value: 'Example'
state: present
- name: Unlink and clear templates from the existing Zabbix template
local_action:
module: community.zabbix.zabbix_template
server_url: http://127.0.0.1
login_user: username
login_password: password
template_name: ExampleHost
clear_templates:
- Example template3
- Example template4
state: present
- name: Import Zabbix templates from JSON
local_action:
module: community.zabbix.zabbix_template
server_url: http://127.0.0.1
login_user: username
login_password: password
template_json: "{{ lookup('file', 'zabbix_apache2.json') }}"
state: present
- name: Import Zabbix templates from XML
local_action:
module: community.zabbix.zabbix_template
server_url: http://127.0.0.1
login_user: username
login_password: password
template_xml: "{{ lookup('file', 'zabbix_apache2.xml') }}"
state: present
- name: Import Zabbix template from Ansible dict variable
community.zabbix.zabbix_template:
login_user: username
login_password: password
server_url: http://127.0.0.1
template_json:
zabbix_export:
version: '3.2'
templates:
- name: Template for Testing
description: 'Testing template import'
template: Test Template
groups:
- name: Templates
applications:
- name: Test Application
state: present
- name: Configure macros on the existing Zabbix template
local_action:
module: community.zabbix.zabbix_template
server_url: http://127.0.0.1
login_user: username
login_password: password
template_name: Template
macros:
- macro: '{$TEST_MACRO}'
value: 'Example'
state: present
- name: Delete Zabbix template
local_action:
module: community.zabbix.zabbix_template
server_url: http://127.0.0.1
login_user: username
login_password: password
template_name: Template
state: absent
- name: Dump Zabbix template as JSON
local_action:
module: community.zabbix.zabbix_template
server_url: http://127.0.0.1
login_user: username
login_password: password
template_name: Template
omit_date: yes
state: dump
register: template_dump
- name: Dump Zabbix template as XML
local_action:
module: community.zabbix.zabbix_template
server_url: http://127.0.0.1
login_user: username
login_password: password
template_name: Template
dump_format: xml
omit_date: false
state: dump
register: template_dump
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The JSON dump of the template Returned: when state is dump and omit_date is no Sample: {“zabbix_export”: {“date”: “2017-11-29T16:37:24Z”, “groups”: [{“name”: “Templates”}], “templates”: [{“applications”: [], “description”: “”, “discovery_rules”: [], “groups”: [{“name”: “Templates”}], “httptests”: [], “items”: [], “macros”: [], “name”: “Test Template”, “screens”: [], “template”: “test”, “templates”: []}], “version”: “3.2”}} |
|
dump of the template in XML representation Returned: when state is dump, dump_format is xml and omit_date is yes Sample: “\u003c?xml version=\”1.0\” ?\u003e\n\u003czabbix_export\u003e\n \u003cversion\u003e4.2\u003c/version\u003e\n \u003cgroups\u003e\n \u003cgroup\u003e\n \u003cname\u003eTemplates\u003c/name\u003e\n \u003c/group\u003e\n \u003c/groups\u003e\n \u003ctemplates\u003e\n \u003ctemplate\u003e\n \u003ctemplate\u003etest\u003c/template\u003e\n \u003cname\u003eTest Template\u003c/name\u003e\n \u003cdescription/\u003e\n \u003cgroups\u003e\n \u003cgroup\u003e\n \u003cname\u003eTemplates\u003c/name\u003e\n \u003c/group\u003e\n \u003c/groups\u003e\n \u003capplications/\u003e\n \u003citems/\u003e\n \u003cdiscovery_rules/\u003e\n \u003chttptests/\u003e\n \u003cmacros/\u003e\n \u003ctemplates/\u003e\n \u003cscreens/\u003e\n \u003ctags/\u003e\n \u003c/template\u003e\n \u003c/templates\u003e\n\u003c/zabbix_export\u003e” |
Authors
sookido (@sookido)
Logan Vig (@logan2211)
Dusan Matejka (@D3DeFi)