Files
portfolio/professional-infra/zabbix-monitoring-incident-response/README.md
T
Mateusz Suski 35e6b139fc
ci / validate (push) Failing after 1m8s
Initial CV-aligned infrastructure portfolio
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.
2026-05-04 17:37:24 +00:00

2.4 KiB

Zabbix Monitoring + Incident Response

Problem

Large Linux/Unix environments need simple, reliable OS checks before more advanced observability becomes useful. Filesystems, CPU, memory, network, process status, proxy backlog, and agent availability must be monitored consistently across Linux and AIX estates.

CV Relevance

This project maps to Zabbix monitoring platform work, proxy maintenance, custom checks, alert noise reduction, and incident response in enterprise environments. It shows operational design and automation without pretending to run AIX locally.

What This Project Demonstrates

  • Ansible-first Zabbix server, proxy, and agent/agent2 configuration structure.
  • Proxy topology for active and passive checks.
  • Linux and AIX OS monitoring templates as reviewable JSON assets.
  • Sample Linux/AIX check data for filesystem, CPU, memory, network, and process monitoring.
  • Runbooks for Zabbix maintenance and incident response.

Architecture

Linux/AIX hosts -> Zabbix agent/agent2 -> Zabbix proxy -> Zabbix server/web
                       |                       |
                       v                       v
                 OS simple checks       proxy queue/cache

Incident -> Alert -> Operator triage -> Maintenance or remediation evidence

Quickstart

cd professional-infra/zabbix-monitoring-incident-response
make test

make test performs Ansible syntax/lint checks and validates the Zabbix template/sample JSON assets.

Validation

ansible-playbook --syntax-check playbooks/*.yml
ansible-lint
python3 scripts/validate_assets.py

Example Output

Sample check payloads are available in samples/linux-os-checks.json and samples/aix-os-checks.json. These show what a reviewable zabbix_sender or API-driven evidence artifact could look like for Linux and AIX hosts.

Interview Talking Points

  • Why Zabbix is suitable for simple OS checks while ELK/Grafana is better for log analysis.
  • How proxies reduce WAN dependency and support branch/client environments.
  • Difference between active and passive checks.
  • How to troubleshoot unsupported items, missing data, proxy backlog, and agent reachability.
  • How Linux and AIX monitoring differ without inventing local AIX runtime.

Roadmap

  • Add API import helpers for templates.
  • Add a Docker-based Zabbix server/proxy demo scaffold.
  • Add Wazuh or security monitoring integration as a separate side lab.