Server & Network Monitoring Features

Device discovery, groups and templates

Add devices and configure their monitoring together.

Discovery: Scan IPv4 networks and address ranges manually or on a schedule; choose which discovered devices to add.
Organisation: Group devices, search names and addresses, and filter by status.
Templates: Reuse services, resources and additional checks; preview changes for selected devices and apply them together.
Setup: Test the selected checks and credentials before saving; configure intervals, timeouts, failure thresholds and metric limits.

Linux servers, processes and disk performance

Follow resource usage and operating status down to each check.

CPU and RAM: Measure processor load, used and free memory; display file system capacity, used space and free space.
Processes and services: Check configured process names for running instances and monitor selected systemd services.
Disk performance: Measure read and write rates, read/write operations per second, busy time and average I/O duration.
Access: Connect Linux through SSH using a password or key; collect suitable resource metrics through SNMP too. System services and disk performance require Linux SSH.

Windows and event logs

Monitor Windows resources and selected services centrally through WinRM with HTTPS.

Resources: Measure CPU usage, memory usage, free RAM and local drive usage.
Windows services: Check selected services for a running state and identify missing or stopped services.
Events: Count error events in the Windows System and Application logs within the selected time window.
Setup: Use the supplied Windows setup script; configure the necessary WinRM access and read permissions on target systems.

Network interfaces and switch ports

Assess connectivity, throughput and errors for individual ports.

Discovery: Detect network interfaces automatically, select ports and specify which connections must be up.
Traffic: Display receive and transmit rates in Mbit/s and utilisation separately for each direction.
Errors: Track receive errors, transmit errors and dropped packets per second; set warning and critical thresholds.
Port speed: Use the reported speed or enter it manually; inspect connection status and port history.

Network quality

Extend reachability checks with packet loss and response-time variation.

Packet loss: Measure the percentage of ICMP test packets that receive no reply.
Response times: Display average, minimum and maximum latency.
Variation: Evaluate differences between consecutive response times as jitter.
Assessment: Set warning and critical thresholds for loss, latency and jitter; follow their history.

Traffic by source

Use NetFlow v5/v9 and IPFIX to identify connections generating traffic.

Reception: Analyse exported flow data from suitable routers and switches with the integrated receiver.
Sources: Show the largest source and destination addresses, protocols and connections with source and destination ports.
Metrics: Capture exported data volume, packets, average rate within the reception window and the last received record time.
Context: Analyse the selected time window; values refer to traffic exported by the network device.

Hyper-V and VMware

Include virtual machines, hosts and datastores in monitoring.

Hyper-V: Discover virtual machines through WinRM HTTPS and check their power and health states.
VMware: Query ESXi or vCenter through vSphere; collect host connection status, power state, CPU and RAM usage.
Virtual machines: Show VMware power state, CPU usage and active guest RAM; specify which VMs should remain running.
Datastores: Monitor accessibility and storage usage; detect missing expected VMs as problems.

MariaDB, MySQL and PostgreSQL

Check databases through login and real read queries.

Connection: Measure connection and read-query duration, open connections, connection limits and connection utilisation.
MariaDB/MySQL: Collect active queries, uptime, queries and slow queries since startup, and failed logins.
PostgreSQL: Display active queries, lock waits, committed and rolled-back transactions, and deadlocks.
Storage and cache: Capture database size and cumulative cache hit ratio; details depend on the database system and read permissions.

Printers and supplies

Collect printer status, supplies and specific device messages through SNMP.

States: Show ready, printing and warming up, plus reported errors such as paper jams, open covers, offline status or maintenance needs.
Supplies: Capture toner, ink and other supply levels as well as waste containers; evaluate warning and critical thresholds.
Paper and counters: Display paper-tray levels and page counts or other totals reported by the print engine.
Checks: Test printer access before saving; identify missing or non-numeric information explicitly.

Server hardware, sensors and SMART

Monitor hardware health alongside operating-system metrics.

Redfish: Check system health, temperatures, fans, power supplies, controllers and drives on compatible iLO, iDRAC and other Redfish systems.
Sensors: Collect available temperatures, fan speeds, voltages and hardware alarms through Linux SSH or supported SNMP sensors.
Linux RAID: Detect missing members of a software RAID and display its state.
SMART: Check overall health of supported drives through Linux SSH. smartctl must be available on the monitored server.

Synology NAS and UPS

Monitor storage appliances and power systems using their own status data.

Synology system: Check system status, temperature, power supplies and available system and CPU fans through SNMP.
Synology storage: Capture drive state, health, temperature and RAID status.
UPS battery: Display battery state, charge, estimated remaining runtime and battery temperature.
UPS operation: Capture mains, battery or bypass operation, output load and active device alarms.

Web services, DNS, mail and certificates

Check service functionality with targeted protocol tests.

Ping and TCP: Check reachability and response time; test whether a configured TCP port accepts connections.
HTTP/HTTPS: Request URLs, measure response times and compare returned HTTP status with expected status codes.
DNS: Query a specific DNS server and optionally compare its answer with an expected record.
Mail protocols: Check SMTP, IMAP and POP3 including TLS/STARTTLS and optional login, without sending or retrieving messages.
TLS certificates: Check remaining validity and certificate trust; set warning and critical thresholds before expiry.

Metric history and thresholds

Compare current states with their development over time.

Periods: Choose histories for one, six or 24 hours, or seven or 30 days.
Charts: Inspect averages, minima and maxima; explore data points with mouse or keyboard and open detailed histories.
Visibility: Identify missing values and failed checks; also view measurements in tables with time and status.
Thresholds: Set warning and critical limits for each measurement. Metrics and events are normally retained for 30 days.

Device connections and dependencies

Document technical relationships alongside monitoring.

Connection map: Manually add and label cable and Wi-Fi connections between devices.
Layout: Arrange devices graphically, select suitable icons and save their positions.
Dependencies: Make a device’s checks depend on an upstream service, such as a connection through a router.
Problem context: Suspend downstream checks when their dependency fails and display the reason on the affected device.

Email notifications and Qisutu integration

Send problems and recoveries to the appropriate destination.

Email: Configure SMTP server, encryption, sender and recipients; add authentication when required.
Qisutu: Forward events to the ticket system’s matching monitoring add-on; configure its connection address and access key.
Scope: Limit delivery to groups or selected devices. Report status changes and recoveries without repeating unchanged problems on every check.
Delivery: Store pending notifications and retry connection failures; test connections without sending test emails or creating tickets.

Teamwork and local operation

Work together in the browser while keeping data on your own server.

Accounts: Create, edit, disable and delete agent accounts; all agents have the same permissions.
Languages: Choose German, English, Czech, Spanish, French, Italian, Dutch, Polish, Brazilian or European Portuguese, or Turkish.
Personal settings: Manage language and password per account; the language choice persists across logins.
Operation: Install on your own Linux server and use HTTPS in the browser. Configuration and metrics remain local; interface libraries are included.