You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to make review (Moniroting as Code). Read more on habr.com: [RU](#), [EN translated](#)
44
+
You want to make review (Moniroting as Code). Read more on habr.com: [RU](#), [EN translated](#)
42
45
1. Fork this repository to you GitLab account or instance (e.g. `groupname/zabbix-review-export`)
43
-
2. Create repository where will be saved XML and YAML (e.g. two repository`groupname/zabbix-xml` and `groupname/zabbix-yaml`. And do first commit (create empty `README.md`)
44
-
3. Create two branches in this repos: `master` and `develop`. In repository `groupname/zabbix-xml` set `develop`[default branch](https://docs.gitlab.com/ee/user/project/repository/branches/#default-branch).
45
-
4. Specify [Project Variables](https://docs.gitlab.com/ee/ci/variables/#variables) for all variables, specified on top in[.gitlab-ci.yml](./.gitlab-ci.yml)
46
-
5. Change jobs in `.gitlab-ci.yml` and Leave the ones you need job in `.gitlab-ci.yml` and change to you environment (see commented examples block).
46
+
2. Create repository where will be saved XML and YAML (e.g. two repositories`groupname/zabbix-xml` and `groupname/zabbix-yaml`. Do first (init) commit (create empty `README.md`).
47
+
3. Create two branches in this repos: `master` and `develop`. In repository `groupname/zabbix-xml` set `develop`as a [default branch](https://docs.gitlab.com/ee/user/project/repository/branches/#default-branch).
48
+
4. Specify [Project Variables](https://docs.gitlab.com/ee/ci/variables/#variables) for all variables, specified on top of[.gitlab-ci.yml](./.gitlab-ci.yml)
49
+
5. Change jobs in `.gitlab-ci.yml` and leave the ones you need job in `.gitlab-ci.yml` and change to you environment (see commented examples block).
47
50
6. Try to run manual job `YAML zabbix`
48
51
7. Create merge request `develop=>master` in `zabbix-yaml`. For first time you can merge without review, it's too hard :)
49
52
8. Configure [Schedule](https://docs.gitlab.com/ee/user/project/pipelines/schedules.html) (eg. every week)
50
53
9. Change some host, template or other [supported objects](#supported-objects) in zabbix, run manual job and create merge request again. Enjoy!
51
54
52
55
### Notes
53
-
Use two different repositories for XML+JSON (raw-format) and readable YAML format:
56
+
Use two repositories for XML+JSON (raw-format) and readable YAML format:
54
57
-`XML` + `JSON` will be useful if you want restore some object after remove or alarge number of changes.
55
-
-`YAML` format is more suitable for people to read and review changes. Also the script removes all empty values.
58
+
-`YAML` format is more suitable for people to read and review changes. The script removes all empty values.
56
59
57
-
Also, after merge we create empty merge request `develop=>master` and receive all notifications at changes (schedule or manual jobs run).
60
+
Create empty merge request `develop=>master`after merge and receive notifications at changes (schedule or manual jobs run) on your email.
58
61
59
62
To answer for the question "Who make this changes?" you need use [Zabbix Audit](https://www.zabbix.com/documentation/4.0/manual/web_interface/frontend_sections/reports/audit). It's difficult but possible.
0 commit comments