Mateusz Suski
35e6b139fc
ci / validate (push) Failing after 1m8s
Rework portfolio around Linux operations, Zabbix monitoring, migration validation, and ELK/Grafana log observability. Add AAP-style LVM resize workflow, Zabbix server/proxy/agent automation assets, Linux/AIX monitoring templates, and updated validation CI.
973 B
973 B
Zabbix Proxy Design
Purpose
Zabbix proxies reduce dependency on direct connectivity between the central server and monitored hosts. They are useful for client networks, segmented environments, remote sites, and maintenance windows.
Active Proxy
- Proxy connects to the Zabbix server.
- Good for restricted networks where inbound access to the proxy is not allowed.
- Hosts can use active agent checks against the proxy.
- Main operational checks: proxy last seen, delayed values, local DB size, config sync.
Passive Proxy
- Zabbix server connects to the proxy.
- Useful when central server can reach the proxy network.
- Requires firewall rules from server to proxy.
- Main operational checks: proxy listener, network latency, poller load.
Operational Signals
- Proxy queue growth.
- Unsupported items after template changes.
- Agent unreachable or active checks delayed.
- Proxy DB growth during WAN outage.
- Config sync failures after maintenance.