MantisNMS · Reference
MantisNMS Sensor Catalog
Every kind of sensor MantisNMS can run today, with one line on what each one checks. The list below has 52 entries, numbered so you can count them: 32 sensor types you add under Monitor → Devices → + Add sensor (the SQL and cloud sensors are listed once per database engine and cloud platform they support, and Hyper-V VMs are picked from a Hyper-V host's VM list), 17 built-in vendor profiles for SNMP devices, and 3 receivers for data your devices send to the probe.
At a Glance
| Group | Entries | Numbers |
|---|---|---|
| Network & availability | 9 | 1–9 |
| Web & certificates | 5 | 10–14 |
| Servers & Windows | 2 | 15–16 |
| Virtualization | 3 | 17–19 |
| Databases & apps | 7 | 20–26 |
| Cloud | 3 | 27–29 |
| SNMP device profiles | 17 | 30–46 |
| Receivers | 3 | 47–49 |
| Custom | 3 | 50–52 |
| Total | 52 |
Sensors run from your MantisNMS probe, inside your network, except the cloud sensors, which are read from the MantisOps cloud. The names below are the ones you see in the console. A sensor type is not a price: see How Sensors Are Counted for what counts toward your plan.
Network & Availability
| # | Sensor | What it checks |
|---|---|---|
| 1 | Ping (ICMP) | Whether a host answers ping, with round-trip time, packet loss and jitter. |
| 2 | TCP port | Whether a TCP port accepts connections, and how long the connection takes. |
| 3 | DNS | Whether a hostname resolves and how long it takes, and optionally that the answer includes an address you expect. |
| 4 | NTP (time) | Whether a time server answers an NTP request, and how quickly. |
| 5 | LDAP | Whether a directory server accepts connections on its LDAP port (389 by default). |
| 6 | RDP | Whether a Remote Desktop port (3389 by default) accepts connections. |
| 7 | SSH | Whether an SSH server answers with a valid SSH greeting. |
| 8 | FTP | Whether an FTP server answers with its ready greeting. |
| 9 | SNMP (interface health) | A switch, router, firewall or server over SNMP v1, v2c or v3: each interface's status, traffic and errors, plus CPU, memory, disks, system details and temperatures when the device reports them. |
Web & Certificates
| # | Sensor | What it checks |
|---|---|---|
| 10 | HTTP | Whether a URL answers with a success status (or the exact status you set) and, optionally, contains a keyword; with response time. |
| 11 | REST / JSON | Calls an API endpoint, reads one field from the JSON response by its path, and checks it matches the value you expect. |
| 12 | TLS (cert expiry) | Reads a server's TLS certificate and reports the days left before it expires. |
| 13 | SSL/TLS security grade | Scores an endpoint's TLS set-up from 0 to 100 with an A–F grade: protocol, cipher, whether old TLS 1.0/1.1 is still accepted, certificate trust and expiry. |
| 14 | HTTP transaction (multi-step) | Runs an ordered series of web requests (for example sign in, then open a page), keeping cookies and checking each step's status and content; reports the total time. |
Servers & Windows
| # | Sensor | What it checks |
|---|---|---|
| 15 | Windows host (WMI / WinRM) | A Windows server or PC without an agent: CPU, memory, free space on each fixed disk and network throughput, plus disk read and write rates when it connects over WinRM. |
| 16 | Redfish (server hardware) | A server's hardware health from its management controller over Redfish, and optionally one numeric reading such as a temperature. |
Virtualization
| # | Sensor | What it checks |
|---|---|---|
| 17 | VMware vCenter | Signs in to vCenter, lists every VM with its power state, and shows live CPU, memory, network and disk use per VM. |
| 18 | Hyper-V host | Lists every VM on a Hyper-V host with its state, CPU, memory, uptime and health, so you can choose which VMs to monitor. |
| 19 | Hyper-V VM | One VM on a Hyper-V host: whether it is running, its CPU and memory, and its network and disk throughput. |
Databases & Apps
| # | Sensor | What it checks |
|---|---|---|
| 20 | Mail (SMTP/IMAP/POP3) | Whether a mail server answers with a ready greeting over SMTP, IMAP or POP3, optionally containing text you expect. |
| 21 | SQL: MySQL / MariaDB | Connects to the database and, optionally, runs a query and checks the value it returns. |
| 22 | SQL: PostgreSQL | Connects to the database and, optionally, runs a query and checks the value it returns. |
| 23 | SQL: Microsoft SQL Server | Connects to the database and, optionally, runs a query and checks the value it returns. |
| 24 | SQL: Oracle | Connects to the database and, optionally, runs a query and checks the value it returns. |
| 25 | MongoDB | Whether a MongoDB deployment accepts the connection and answers a ping. |
| 26 | Redis | Whether a Redis server answers PING and, optionally, that a key holds the value you expect. |
The SQL, MongoDB and Redis sensors take a connection string. A password in it is stored write-only: MantisNMS shows it as •••• everywhere and sends it only to the probe that runs the check. To keep the saved password when you edit the sensor, leave •••• in place; to change it, type the new password over it. Use a read-only database account. The same applies to a password in the URL of an HTTP, REST API or HTTP transaction sensor (https://user:password@host/path).
Cloud
The Cloud metric sensor reads the latest value of a metric from your cloud provider's monitoring service, using read-only credentials you save in the Customer Portal. It is read from the MantisOps cloud, so no probe is needed.
| # | Sensor | What it checks |
|---|---|---|
| 27 | Cloud metric: AWS CloudWatch | Any CloudWatch metric by namespace, name and dimensions (for example EC2 CPU utilization). |
| 28 | Cloud metric: Azure Monitor | Any Azure Monitor metric for a resource (for example a VM's CPU percentage). |
| 29 | Cloud metric: Google Cloud Monitoring | Any Cloud Monitoring metric in a project, chosen by a metric filter. |
SNMP Device Profiles
On an SNMP sensor, a vendor MIB profile adds the vendor's own health readings on top of interfaces and host resources. MantisNMS picks the profile from the device's discovered make, or you choose one; fan, power-supply, disk and battery status roll up to alerts. You can see each profile's readings, and add your own, under Settings → MIB Profiles.
| # | Profile | What it reads |
|---|---|---|
| 30 | Cisco (IOS / IOS XE / NX-OS) | CPU, memory and temperatures, and fan, power-supply and voltage state. |
| 31 | Cisco Meraki | Each device's name, status and client count, read from the Meraki cloud's SNMP service. |
| 32 | Juniper (Junos) | CPU, memory, temperature and component operating state. |
| 33 | Fortinet FortiGate | CPU, memory, session count, temperatures and hardware sensor alarms. |
| 34 | Palo Alto (PAN-OS) | Active sessions, session table use and CPU per core. |
| 35 | SonicWall (SonicOS) | CPU, memory and connection count. |
| 36 | HPE / Aruba ProCurve (ArubaOS-Switch) | CPU and memory. |
| 37 | Extreme Networks (EXOS) | CPU, memory and temperature. |
| 38 | MikroTik (RouterOS) | CPU load, board and CPU temperature, and voltage. |
| 39 | Synology (DSM NAS) | System, power and fan status, temperatures, CPU, memory, and each disk's and RAID volume's status. |
| 40 | QNAP (QTS NAS) | CPU use, system temperature and memory. |
| 41 | NetApp (Data ONTAP 7-mode) | Overall status, NVRAM battery, failed fans, power supplies and disks, and CPU busy. |
| 42 | Dell iDRAC / OMSA (PowerEdge) | Overall health, temperatures, fans, power supplies and physical disk state. |
| 43 | HPE iLO / Insight (ProLiant) | Thermal, fan and power-supply condition, temperatures and physical drive status. |
| 44 | APC UPS (PowerNet) | Battery capacity, temperature and status, runtime left, output load and status, input voltage and the replace-battery warning. |
| 45 | Standard UPS (UPS-MIB) | Battery charge, status, voltage, temperature and runtime, output load and source, and input voltage, on any UPS that supports the standard UPS-MIB. |
| 46 | Standard printer (Printer-MIB) | Toner and other supply levels and the lifetime page count, on any printer that supports the standard Printer-MIB. |
Also built in but not counted above, because they read only standard values: a generic host-resources profile, a standard ENTITY-SENSOR profile for the temperature, fan and voltage sensors many switches report, and basic CPU and load profiles for Ubiquiti EdgeOS and Cato Sockets.
Receivers
Receivers collect what your devices send to the probe. Point the device at the probe's address; see Syslog & SNMP Traps and Flow Monitoring.
| # | Receiver | What it collects |
|---|---|---|
| 47 | Syslog | Syslog messages on UDP 514 from devices you monitor, searchable under Respond → Events. |
| 48 | SNMP traps | SNMP v1 and v2c traps on UDP 162, searchable under Respond → Events. |
| 49 | Flow (NetFlow v5/v9, IPFIX, sFlow) | Flow exports from routers and switches, shown as top talkers, conversations and applications per exporter and interface. |
Custom
| # | Sensor | What it checks |
|---|---|---|
| 50 | SNMP custom OID | Reads any SNMP OID you enter and, optionally, checks it matches a value you expect. |
| 51 | SSH command (custom) | Signs in over SSH and runs a command you define: up when it succeeds, optionally checking its output for text you expect; a numeric result can drive alert rules. |
| 52 | Custom script | Runs a script you placed in the probe's scripts folder and reads the status, value and message it returns. |
Plus any SNMP OID, REST/JSON endpoint, SSH command or script you define.
Tell us through our support page or email support@mantisops.net. We respond within one business day.