Is there a way to implement peer review in config changes within zabbix? Things like changing trigger thresholds and adding new templates. We manage most of zabbix relations externally via the API.
We'd like to empower all of our coworkers to make changes in the monitoring system and we'd like to have a conversation around it. The auditing functionality is ok but that is more of a reactive than proactive solution. The best solution I have come up with so far is to write some tooling around a work flow that involves fetching the config xml dump out of our code repository, spinning up a VM, importing the current config, making changes in the gui, exporting config, committing changes and creating a pull request for peer review. Upon peer review, implementing more tooling (possibly scary stuff) to then deploy the config and import it.
Thoughts?
We'd like to empower all of our coworkers to make changes in the monitoring system and we'd like to have a conversation around it. The auditing functionality is ok but that is more of a reactive than proactive solution. The best solution I have come up with so far is to write some tooling around a work flow that involves fetching the config xml dump out of our code repository, spinning up a VM, importing the current config, making changes in the gui, exporting config, committing changes and creating a pull request for peer review. Upon peer review, implementing more tooling (possibly scary stuff) to then deploy the config and import it.
Thoughts?