Network Monitor (Zabbix / PRTG)

Basic Information

Field	Value
Category	Infrastructure
Owner	Filip Kohák
Deputy	Artem Ryzhkov
SLA	24x7
Deployment	On-prem VM (Proxmox cluster)

Description

Network Monitor tracks availability and performance of the corporate infrastructure. The system monitors servers, network devices, VMs, and key services, sending alerts to Slack.

Monitored objects:

• Physical servers (Proxmox nodes, Windows Server)
• Network devices (FortiGate, switch, AP)
• Virtual machines (availability, CPU, RAM, disk)
• Key services (Active Directory, DHCP, DNS)
• UPS (power status, temperature)

Alert channel: Slack #it-alerts

Access and Login

• URL: http://[monitor-vm-ip] (internal network or VPN)
• Login: admin account (stored in Passbolt)
• Read-only access for L1 team (Tomáš, Jakub)

Procedure — Add New Device to Monitoring

Zabbix

1. Configuration → Hosts → Create Host
2. Fill in: Hostname, IP address, Groups
3. Add Interface (SNMP or Zabbix Agent)
4. Select appropriate Templates (Linux, Windows, FortiGate, UniFi…)
5. Save — monitoring starts automatically

Alert Thresholds

Metric	Warning	Critical
CPU usage	>70% for 5 min	>90% for 2 min
RAM usage	>80%	>95%
Free disk space	<20%	<10%
Ping availability	>50ms	timeout / 100% packet loss

Procedure — Respond to an Alert

1. Verify if it's a real issue (false positive vs. actual outage)
2. Log in to monitoring system and check details
3. Acknowledge alert (prevents repeated notifications for same issue)
4. Begin diagnostics and escalation per SLA

Procedure — Add Maintenance Window

Before planned downtime:

1. Configuration → Maintenance → Create Maintenance
2. Set time interval and select affected hosts
3. Monitoring won't send alerts during the window

Related Guides

• Proxmox — monitored VMs and hosts
• FortiGate — monitored network device

Contact

• Owner: Filip Kohák — Slack @filip
• Deputy: Artem Ryzhkov — Slack @artem
• Alerts: Slack #it-alerts