# Agent Monitoring

Applications Manager supports **agent-based monitoring** using the **FSO (Full Stack Observability) Agent**. The FSO Agent is a lightweight component installed on the target server to collect detailed performance metrics and logs from servers and applications. Unlike agentless monitoring, the FSO Agent collects data locally and securely transmits it to the Applications Manager server, providing enhanced visibility and reliability in monitoring.

## Key components of agent-based monitoring

The FSO Agent consists of multiple sub-agent that work together to provide comprehensive monitoring:

- **Server monitoring** — Collects system-level performance metrics such as CPU, memory, disk, and processes.
- **Application Logs (AppLogs) monitoring** — Monitors application logs and helps in log analysis and troubleshooting.

These components operate together under the FSO Agent framework to deliver unified observability.

## Prerequisites for agent-based monitoring

The prerequisites listed below are applicable for both Windows and Linux devices:

### 1. Hardware requirements

These are the minimum specifications required in the device where the FSO agent will be installed:

| Parameter | Windows | Linux |
|---|---|---|
| Processor speed | 1.0 GHz | 1.0 GHz |
| RAM | 512 MB | 512 MB |
| Hard disk space | 250 MB | 500 MB |

### 2. Supported OS versions

The FSO agent supports all major versions of Microsoft Windows and Unix systems as listed below:

| Software | Versions Supported |
|---|---|
| **Windows OS** |  |
| Windows OS | Windows 11 / Windows 10 / Windows 8.1 / Windows 8 / Windows 7 / Windows Vista |
| Windows Server OS | Windows Server 2025 / 2022 / 2019 / 2016 / 2012 & 2012 R2 / 2008 & 2008 R2 |
| **Linux OS** |  |
| Ubuntu | 14.04 and above (x86_64)<br>16.04 and above (Armv8 64bit) |
| Debian | Debian 7 "Wheezy", Debian 8 "Jessie", Debian 9 "Stretch" and above |
| Red Hat | 6 and above |
| CentOS | 6 and above |
| CentOS Stream | 8 and above |
| Rocky Linux | 8 and above |
| AlmaLinux | 8 and above |
| SUSE | SUSE 11 and above, SLES 12 and above, open SUSE 15 and above |
| Fedora | Fedora 26 and above (x86_64)<br>Fedora 27 and above (ARM v8 64bit) |
| Mandriva Linux | 21.1 and above |
| Gentoo Linux | 3.0.31 and above |
| Linux Mint | 6 and above |

### 3. Port requirements

To ensure smooth functioning of agent-based monitoring in Applications Manager, the following ports need to be opened/available in the firewall, with respect to the device being monitored.

| Port | Protocol | Direction | Description |
|---|---|---|---|
| Applications Manager web server port (https) | TCP | Outbound | Used for communicating with the Applications Manager server to transmit data. **(10099 by default)** |

### 4. Communication between the server and FSO agent

Before starting the installation process, ensure that the FSO agent web client is accessible in the browser from the target server where you plan to install the agent.

## Agent Resource Consumption

The following outlines the average resource consumption of the **FSO Agent** on supported platforms:

### Windows Server Monitoring agent

The **Windows server monitoring agent** was tested on a basic Windows Server 2019 Datacenter edition with a 1-core Intel Xeon Platinum 2.6GHz processor and 4GB RAM. The results were as follows:

- **CPU Utilization:** Approximately 0.15%
- **Memory Usage:** Around 150 MB of RAM
- **Disk Space Usage:** Approximately 250 MB
- **Network Bandwidth Usage:** Up to 1500 Bytes/sec

### Linux Server Monitoring Agent

The **Linux server monitoring agent** underwent resource consumption testing on a basic Linux server with a 1-core Intel i7 processor, 4GB RAM, and 100GB disk space. The results were as follows:

- **CPU Utilization:** Approximately 0.6%
- **Memory Usage:** Around 200 MB (RSS)
- **Disk Space Usage:** Approximately 500 MB
- **Network Bandwidth Usage:** Up to 1500 Bytes/sec

**Note:** These results were obtained with the agent running without additional plugins, log management (AppLogs) services, or applications in the specified environment. Changes to configuration or environment may impact resource consumption.