Syncing templates to multiple Zabbix servers

[mcbrineellis]

Hi there,

First of all - awesome project! I can't believe that a tool like this hasn't existed until now, great job for making it a reality.

I currently manage my Zabbix templates using Ansible playbooks with the community.zabbix collection and duct tape, and I have a whole bunch of Zabbix servers that I want to keep in sync with a single git repo of templates. I imagine this is a perfect use case for ZabbixCI?

I assume I could run ZabbixCI against a group of servers using a git repo as a single source, by creating multiple config files with the respective URLs of the Zabbix servers and the same source git repo? Then I could build out CI pipelines to run that on a schedule or something. Is there any potential issues with this setup?

Any guidance would be appreciated!

Connor

[q1x]

Hi there! This is very much the use case we had in mind. Our team used to manage around 10 different Zabbix servers and used some custom scripts on top of Salt to manage the templates.

We've decided to improve on this idea by implementing ZabbixCI. Our recommendation would be to use one Zabbix instance as your preferred template dev environment and use that to push to a dev branch in your git repo. After testing/validation you could use a pull request to merge into main and sync to your other servers from there.

However, there is nothing stopping you from using another sync strategy if that better suits your workflow.
You could just as well push and pull from different instances as long as you properly manage any merge conflicts if they arise.

Please give it a try and let us know if you run into issues! Keep in mind to use a fresh git repo as ZabbixCI expects a certain way of template organisation.

Regards,

Raymond

[mcbrineellis]

Thanks for the quick feedback!

I am still setting up this workflow but will report back here with any quirks or tips based on my experiences!