Network monitoring

SNMP and network monitoring

For MSPs who look after the whole office, not just the PCs. Switches, routers, firewalls, printers, storage and battery backups are monitored beside the computers, with syslog collection and an outside check on the internet circuit. No agent goes on the network gear.

Inside Revolutionary RMM · SNMP node

Revolutionary RMM SNMP node with gauges, trends and an interface tableRevolutionary RMM SNMP node with gauges, trends and an interface tableRevolutionary RMM SNMP node with gauges, trends and an interface table

One node, with gauges, trends and its interface table. Product capture with fictional customer names.

What it does

Device classes that already know what to ask.

Choose what a node is and the platform polls the right identifiers for it. There is no management information base (MIB) to import.

How it works

A relay at the site does the polling.

01

Run a relay

The relay runs on a machine you already manage at the customer's site.

02

Add the devices

Add each node by hand or from a template, and choose its device class.

03

Poll over SNMP

The relay polls with SNMP v2c or v3 and the readings appear in the same dashboards and alerting as your computers.

04

Collect syslog

Devices send syslog to the same relay. Sources register themselves and common formats are parsed.

Syslog and circuits

The rest of a network problem.

Inside Revolutionary RMM · Syslog

Revolutionary RMM syslog view with parsed eventsRevolutionary RMM syslog view with parsed events

Collected syslog events, parsed into readable lines. Product capture with fictional customer names.

Limits

What it does not do yet.

Limits

  • There is no automatic network discovery and no topology map yet.
  • Devices are added by hand or from a template.
  • Each site needs one managed computer to host the relay.
  • Not for you yet if you need automatic discovery or a live network map on day one.

Not in the product today: network discovery per location, and one connected asset record across agent, network, mobile and manual sources.

See the roadmap →

Questions

Good to know.

No. A relay running on a machine you already manage polls them over SNMP and receives their syslog.

SNMP v2c and v3. Version 3 supports authentication and privacy, including a context name for devices that need one.

No. Pick the device class (switch, router, printer, battery backup, storage) and the right identifiers are polled for you.

Not yet. Today you add devices by hand or from a template. Discovery per location is on the roadmap.

The circuit is pinged from outside the customer's network, so an outage is detected even when every device inside is unreachable.

Keep exploring

Limits, checked daily

Not in the product today.

Each line below is a gap recorded against this capability in the product's own feature record. A line leaves this page by itself on the next daily run once that record says the gap is closed, so the list cannot fall behind what we ship. The rest of this page is written by hand.

  • A device shows the address it holds now, not a history of the addresses it has held.
  • Uptime checks cover ping, SNMP by device class, syslog and cloud service status; web, port, name service, mail server and real-browser checks are not built yet.
  • Expiry is watched for mail domain records and application credentials, not for a web server's encryption certificate.
  • A device on site can relay SNMP and receive syslog, but agentless checks against Windows management or a database are not built yet.
  • Network equipment is polled over SNMP and sends syslog; reading a vendor's own controller for its client lists and its own alerts is not built yet.

Next step

Bring us the network gear you worry about.

Half an hour on a call. We will walk through how it would sit beside the computers you already manage.