Requirements on host machines
This page lists the minimum hardware and software requirements to install Mugnsoft. You can run all Mugnsoft’s components on the same host server as a standalone machine or in a distributed architecture.
Mugnsoft requirements
To run Mugnsoft, you must have a supported operating system, hardware that meets or exceeds minimum requirements, and a supported browser
Supported operating systems
Packages are built for 64-bit x86 (amd64) only.
| System | Versions | Service manager |
|---|---|---|
| Windows | Windows 10 / 11, Windows Server 2016 and later (older Windows cannot run the binaries) | Windows services |
| Debian / Ubuntu | tested on Debian 12, Ubuntu 22.04 and 24.04 | systemd (Upstart / SysV detected too) |
| RPM-based | tested on RHEL / AlmaLinux 8 (Rocky, CentOS Stream, Fedora: same family) | systemd |
All components can run on one host, or each on its own (one component of each kind per host). Docker and Kubernetes images also exist, see Install on Docker and Install a probe on Kubernetes.
Note:
Network flows
Every component listens on its own API port and the Webserver connects back to it, so open both directions:
| From | To | Port (default) | Why |
|---|---|---|---|
| Users’ browsers | Webserver | TCP 9090 (PortWEB in webserver.json) |
Web UI |
| Monitors, Integrators, Sentinel Agents | Webserver | TCP 8050 (PortAPI) |
Registration and data push |
| Webserver | each Monitor / Integrator / Sentinel Agent | its port (packages: monitor 8072, integrator 8060, sentinel 8078) |
The Webserver drives the component |
| Monitors | the services they test | depends on each monitor | The checks themselves |
| Integrators | your tools (ITSM, chat, email, metrics) | depends on each output | Notifications and data export |
| Webserver (ADMIN) | Webserver-Front | TCP 8040 (FRONT’s PortAPI) |
Replication, see Webserver-Front |
All of them are HTTPS. Downloads and webdrivers also need outgoing HTTPS to mugnsoft.com and the browser vendors’ sites, or a manual copy.
Hardware recommendations
The following table describes the hardware (CPU and memory) requirements recommended for the Mugnsoft’s components
| server type | Deployment | Number of Processors | Physical Memory |
|---|---|---|---|
| webserver | Standard (up to 10 probes) | 4 CPU cores | Minimum: 8 GB RAM<br> Recommended: 12 GB RAM |
| webserver | Large (up to 20 probes) | Minimum 8 CPU cores | Minimum: 12 GB RAM<br> Recommended: 24 GB RAM and up |
| probe | Standard (up to 100 monitors) | 4 CPU cores | Minimum: 8 GB RAM<br> Recommended: 12 GB RAM |
| probe | Large (up to 200 monitors) | Minimum 8 CPU cores | Minimum: 12 GB RAM<br> Recommended: 24 GB RAM and up |
| integrator | Standard (up to 10 probes) | 4 CPU cores | Minimum: 8 GB RAM<br> Recommended: 12 GB RAM |
| integrator | Large (up to 20 probes) | Minimum 8 CPU cores | Minimum: 12 GB RAM<br> Recommended: 24 GB RAM and up |
Packet capture runtime (Sentinel Agent only)
The Sentinel Agent derives its network bandwidth figures from captured packets, so a host that should report bandwidth needs a pcap runtime and the privilege to open it. Nothing is required to install or upgrade the agent itself — this is a runtime dependency only.
| Platform | Install | Privileges |
|---|---|---|
| Windows | Optional: the Npcap runtime installer from npcap.com. The SDK is not needed. Without Npcap, bandwidth is measured from Windows TCP statistics, with restrictions: no protocol detection from the payload, short connections missed, slightly lower figures. | Administrator / LocalSystem: always without Npcap; with Npcap, when it was installed with Restrict driver access to Administrators only. |
| Linux (any distribution) | Nothing: libpcap is built into the agent since 4.2.0. | CAP_NET_RAW — run as root, or setcap cap_net_raw+ep <agent binary>. |
Agents older than 4.2.0
If a host still runs an agent older than 4.2.0, that agent links libpcap dynamically. Without it, the agent does not start at all:
error while loading shared libraries: libpcap.so.0.8: cannot open shared object file: No such file or directory
- Debian / Ubuntu:
apt install libpcap0.8 - RHEL / CentOS / Fedora:
dnf install libpcap, then create the name the old binary looks for:
ln -s /usr/lib64/libpcap.so.1 /usr/lib64/libpcap.so.0.8
Upgrading the agent to 4.2.0 or later removes the need for both; the package and the link can stay, they are no longer used.
Note:
Supported web browsers
The Web UI supports the current versions of Chrome, Edge, Firefox and Safari.
On monitor probes running EUM journeys, the browser and its webdriver must have the same major version. If the probe cannot download the webdriver itself, disable the browser’s automatic updates so the two do not drift apart (see the browser section of Install on Linux or Install on Windows).