feat: suppress System name changed trigger for Zabbix server host #59

New issue

Closed

opened 2026-05-15 21:46:02 +00:00 by mconway · 0 comments

mconway commented

2026-05-15 21:46:02 +00:00

Owner

The Zabbix server host has had an active [Info] System name has changed problem since 2023 because the Zabbix server pod name changes on every K8s restart (e.g. zabbix-zabbix-server-6c589dc649-x7w87).

This is noise — the pod name is not meaningful as a hostname.

Options

Add a Zabbix maintenance period for this specific trigger on the Zabbix server host (manageable via community.zabbix.zabbix_maintenance)
Override the visible hostname on the Zabbix server host to a static value via the Helm values
Add a trigger override/suppression tag in the role

Tasks

Decide on approach
Implement via the k8s-zabbix role so it is applied on every deploy

The `Zabbix server` host has had an active `[Info] System name has changed` problem since 2023 because the Zabbix server pod name changes on every K8s restart (e.g. `zabbix-zabbix-server-6c589dc649-x7w87`). This is noise — the pod name is not meaningful as a hostname. ## Options - Add a Zabbix maintenance period for this specific trigger on the Zabbix server host (manageable via `community.zabbix.zabbix_maintenance`) - Override the visible hostname on the Zabbix server host to a static value via the Helm values - Add a trigger override/suppression tag in the role ## Tasks - [ ] Decide on approach - [ ] Implement via the `k8s-zabbix` role so it is applied on every deploy