To make using the Community template repository convenient for all community members, we ask our contributors to follow the practices described on this page.
Each template should be placed in a separate folder inside the correct category. The name of the folder should start with template_ (for example, template_linux_services)
Inside the template_<name> directory should only be separate directories for each Zabbix version the template works with in the format X.X, where X.X stands for the number of major Zabbix version (5.0, 5.4, etc.).
Each version directory may contain only: - one template file (XML, JSON, or YAML) - a documentation file (README.md) - a directory files.
All the additional files, such as executable external check scripts, images, auxiliary utilities, integrations with third-party systems, should be placed into the files directory.
Uploading templates as compressed files is not allowed.
Correct directory structure:
template_<name>[a-z_]{4+}
\_5.0
| \_template_<name>[a-z_]{4+}.xml
| |_README.md
| |_files
| \_other_files
| |_ ...
|_5.4
| \_template_<name>[a-z_]{4+}.[xml,yaml,json]
| |_README.md
| |_files
| \_other_files
| |_ ...
|
|_...
Incorrect directory structures:
Missing version directory:
Several template files:
template_<name>
\_5.0
| \_template_file_1.xml
| |_template_file_2.xml
| |_template_file_3.xml
| |_README.md
| |_files
| \_other_files
| |_ ...
Compressed files are not allowed:
All files in the same directory:
All template files must contain a complete set of templates on which they depend. This ensures the proper template import even into a clean Zabbix server installation.
All community templates are published under the MIT license. Third-party licenses, even the compatible ones (for example, GPL v2/v3) are not accepted.