SSM Server monitoring

With or without an agent. Your choice.

Netronus monitors Linux and Windows servers and their hardware on one screen. Agentless over SSH, WinRM, SNMP and Redfish where an agent cannot be installed; with the lightweight Netronus Agent where you need detail. When you move to the agent later, the same asset is enriched and its history and alarm rules are kept.

Request a demo See capabilities

Monitoring › Servers: agent-based and agentless servers, top consumers and file systems about to fill up

The problem

What gets in the way today

Agent approval processes

In government and finance, installing an agent on every server needs long approvals, and monitoring waits.

Shallow data

Ping and basic SNMP do not show service state, processes, installed packages or disk health.

Heavy, exposed agents

Agents that use hundreds of MB of memory and wait for inbound connections raise both resource and security concerns.

The solution

The right method per asset

Choose the method each server needs and combine several if you like. Agentless and agent-based collection write to the same metric dictionary, so dashboards, alarms and reports do not care where the data came from. The Data coverage card on the asset page shows which data is arriving and what needs an agent or SSH/WinRM credentials.

Linux: SSH (key based, read-only commands only)
Windows: WinRM (HTTPS)
SNMP for both (HOST-RESOURCES-MIB)
Hardware: Redfish for iDRAC, iLO, XClarity, Supermicro
Netronus Agent: a single binary for Linux and Windows

Agentless

Nothing to install on the server

SSHLinux, read-only commands
WinRMWindows over HTTPS
SNMPHOST-RESOURCES-MIB
RedfishiDRAC, iLO, XClarity, Supermicro

Netronus Agent

In-depth, from inside the OS

~20 MBmeasured memory
~0.1%of one CPU core
mTLSoutbound only, no open ports
Bufferno data loss on outages

Upgrade any asset to the agent later; history and alarm rules are kept.

Capabilities

What you get

Lightweight Netronus Agent

Measured footprint: about 20 MB of memory and about 0.1% of one CPU core (default profile, one-minute collection).

No open ports, mTLS

The agent does not listen; it only makes outbound connections. Enrollment uses a one-time token, everything after that is mutual TLS (mTLS).

No data loss during outages

When the server is unreachable the agent buffers data on disk and sends it in order once the connection is back, so charts have no gaps.

Detailed operating system data

Per-core CPU, memory, load, disk and network I/O, file systems, top processes, services and restart counts.

Hardware and disk health

SMART, mdraid, LVM, ZFS and multipath state; fans, power supplies, temperatures, RAID and hardware logs via Redfish.

Inventory and packages

Hardware, BIOS, serial number, installed packages and updates; versions feed CVE matching through security content.

Custom checks

TCP, HTTP(S), certificate expiry and local script checks, managed centrally as profiles.

Central profile management

Collection intervals and service and process selections are assigned as profiles and applied without restarting the agent.

Bulk agent rollout

For the servers you select, Netronus generates asset-bound tokens and one installer script (bash / PowerShell) to distribute with Ansible, GPO or SCCM.

Upgrade the same asset

An enrolling agent attaches to the existing asset by BIOS/VM UUID; no duplicate is created. While the agent is online, agentless collection pauses, so there are no double alarms.

Agent-based or agentless

Pick the depth per server

Start agentless; add the agent only where you need more. Both write the same metrics, so dashboards and alarms keep working.

Data	Agentless (SSH, WinRM, SNMP, Redfish)	Netronus Agent
CPU, memory, load, swap	1 min	10 s – 1 min
File system usage
Service state		+ restart count
Installed packages and updates	partial
Top processes, watched processes	partial
Fans, power supplies, temperature, RAID (Redfish)		partial
SMART, LVM, ZFS, mdraid, multipath	partial
Custom checks (TCP, HTTP, certificate, script)	–
Local buffer during outages	–
What you install	Nothing; an account and network access	One command or MSI; outbound connection only

Screenshots

See it in the product

Server page: performance summary, hardware details and monitoring methods

Data coverage card: which data comes from which method and what needs an agent

Technical summary

At a glance

Item	Detail
Agentless methods	SSH (Linux), WinRM HTTPS (Windows), SNMP v2c/v3 (HOST-RESOURCES-MIB), Redfish 1.6+
Supported BMCs	Dell iDRAC 9, HPE iLO 5/6, Lenovo XClarity Controller, Supermicro X11+
Netronus Agent	Linux (x86_64, arm64; RPM/DEB) and Windows (MSI, runs as a service)
Agent connection	Outbound only; encrypted with mTLS
Measured footprint	About 20 MB of memory, about 0.1% of one CPU core (default profile)
Sampling	Agent: 10 s – 1 min; agentless methods: 1–5 min
Outage buffer	On disk, size-limited; sent automatically when the connection returns
Licensing	Agentless and agent-based servers are counted separately; agent licenses only for the servers you want in depth

Roadmap

Coming next

These items are planned and not part of the current release.

Roadmap Remote (push) installation of the agent and signed remote agent updates
Roadmap Windows event log and Linux journald records in the log module
Roadmap Kerberos authentication for WinRM and SSH

See Netronus in your own environment

We will set up a demo on your network, show the screens with your own devices and prepare a quote for the modules you need.

Request a quote Request a demo