# Experiment 4 – Network Monitoring Using Zabbix

Objective: Monitor a Linux application server using Zabbix to track CPU, memory and network utilization, identify performance anomalies and configure alerts.

## 1. What is Zabbix?

Zabbix is an open-source infrastructure monitoring tool used to monitor servers, networks, applications and other IT resources.

It collects performance metrics, displays them through dashboards and generates alerts when abnormal conditions occur.

## 2. What are the main components of Zabbix?

- Zabbix Server: Central component that collects and processes monitoring data.
- Zabbix Agent: Software installed on monitored machines to collect system metrics.
- Database: Stores collected metrics, configurations and historical data.
- Web Interface: Used to view dashboards, graphs, hosts and alerts.

## 3. What is a Zabbix Agent?

Zabbix Agent is software installed on a monitored device. It collects information such as CPU utilization, memory usage, disk space and network statistics and sends it to the Zabbix server.

## 4. What is a Host in Zabbix?

A host is any device or system being monitored by Zabbix, such as a Linux server, Windows machine, router or network switch.

Each host can have multiple monitoring items associated with it.

## 5. What are Items in Zabbix?

Items are individual metrics or parameters collected from a monitored host.

Examples:

- CPU utilization.
- Available memory.
- Disk space usage.
- Network traffic.

Items define what data Zabbix collects and monitors.

## 6. What are Triggers in Zabbix?

Triggers are conditions or expressions that evaluate collected monitoring data.

When a condition becomes true, Zabbix generates a problem event.

Example: Generate an alert if CPU utilization remains above 80%.

## 7. What are Templates in Zabbix?

Templates are predefined collections of monitoring items, triggers, graphs and other configurations.

They can be linked to multiple hosts, reducing the need to configure each host individually.

## 8. What is the difference between an Item and a Trigger?

- Item: Collects a particular metric, such as CPU utilization.
- Trigger: Evaluates that metric against a condition and generates an alert if the condition is met.

Example: An item collects CPU usage, while a trigger detects when it exceeds 80%.

## 9. How does Zabbix monitor CPU, memory and network utilization?

Zabbix Agent collects system performance metrics from the monitored host and sends them to the Zabbix server.

The server processes and stores the data, which can then be viewed through graphs and dashboards.

## 10. What is a monitoring anomaly?

An anomaly is an unusual or unexpected change in system performance.

Examples:

- Sudden increase in CPU utilization.
- Unexpected memory consumption.
- Abnormally high network traffic.
- Low available disk space.

## 11. What is the difference between a Problem and an Event in Zabbix?

An event is a recorded occurrence in Zabbix, such as a trigger changing state.

A problem represents a detected abnormal condition that requires attention.

## 12. What is the purpose of Zabbix dashboards?

Dashboards provide a visual representation of infrastructure health using graphs, charts, widgets and monitoring information.

They help administrators quickly identify performance issues.

## 13. What happens when a Zabbix Agent becomes unavailable?

The Zabbix server cannot collect metrics from that agent. The host may show an unavailable or unreachable status, and a corresponding alert can be generated if configured.

## 14. What is the difference between Zabbix and SNMP?

- Zabbix: A complete infrastructure monitoring platform.
- SNMP: A protocol used to monitor and manage network devices.

Zabbix can use SNMP to collect information from network devices.

## 15. How would you configure an alert for high CPU utilization?

First, configure a CPU monitoring item for the host. Then create a trigger with a condition such as CPU utilization exceeding 80%.

When the condition is satisfied, Zabbix generates a problem event, which can be used to notify the administrator.

## Last-minute revision

| Term          | Remember                          |
| ------------- | --------------------------------- |
| Zabbix Server | Collects and processes data       |
| Zabbix Agent  | Collects host metrics             |
| Host          | Monitored device                  |
| Item          | Metric being collected            |
| Trigger       | Condition that generates an alert |
| Template      | Reusable monitoring configuration |
| Dashboard     | Visual monitoring interface       |
| Event         | Recorded occurrence               |
| Problem       | Detected abnormal condition       |
| Anomaly       | Unusual system behaviour          |

Important for practical viva

Focus on:

1. Zabbix architecture and components.
2. Zabbix Server vs Agent.
3. Host, Item and Trigger.
4. Templates and dashboards.
5. How CPU, memory and network metrics are collected.
6. How triggers generate problem events.
7. Zabbix vs SNMP.

Based on Experiment 4 of your CS414 lab question bank.&#x20;

CS414_ITIMM_Lab_ESE.pdf
