Skip to main content

Device Monitor

Device Monitor is the registry and health system for everything on your network that isn't an edge node: switches, firewalls, PLCs, HMIs, protocol gateways, and sensors. It registers them, polls them, and tells you when one stops answering.

Edge nodes are handled by Ops. Device Monitor covers the equipment around them.

The Devices tab under Sites with counters for devices, online, offline, and unknown, a Register device button, Import CSV, and filters for type and health

EmberCORE Sites: Devices. Register the equipment around your nodes and watch its health.

In the console, devices are under Sites, then Devices. The counters say how many devices are registered, online, offline, and unknown. Register device adds one, Import CSV adds many, and the search box and the type and health filters find them again. A tenant with nothing registered says so and tells you how to start.

The health panel​

Devices live inside your site hierarchy, so you reach them by selecting a site and then a building. Four counters summarize what you find:

CounterMeaning
HealthyResponding to health checks normally
WarningResponding, but with elevated error rates or latency
CriticalUnreachable, or reporting a fault
UnknownRegistered but never successfully polled

Unknown is worth treating differently from Critical. Critical means something that was working has stopped. Unknown almost always means the device was registered with the wrong address or the wrong SNMP credentials and has never worked at all.

Registering devices​

You can register devices one at a time or by bulk import. Each one needs an address, a type, and, if you want more than reachability, SNMP credentials.

TypeTypical use
SwitchManaged Ethernet switches
FirewallNetwork security appliances
PLCProgrammable logic controllers
HMIHuman-machine interfaces
GatewayProtocol converters
SensorEnvironmental sensors
CustomAny other IP-connected device

The type drives which panels you get. Registering a switch as Custom still monitors it, but you lose the port grid.

What polling gives you​

With reachability only, you get up or down. With SNMP configured, you also get:

  • Port grid, a visual map of switch port status and utilization
  • Interface status, per-port link state, speed, errors, and traffic counters
  • Sparklines, recent trend for each metric alongside its current value

Health checks run on a periodic schedule, and you can also trigger one on demand when you want an answer now rather than at the next interval.

Industrial protocol metrics​

Beyond SNMP, Device Monitor can collect from equipment over the protocol it already speaks. Sixteen are supported: eleven natively and five through a gateway or controller that speaks one of the native ones.

ProtocolDefault portTypical equipment
OPC UATCP 4840PLCs, SCADA, industrial gateways
Modbus TCPTCP 502Drives, meters, sensors
BACnet/IPUDP 47808Building automation, HVAC
EtherNet/IP (CIP)TCP 44818Allen-Bradley and Rockwell controllers
S7commTCP 102Siemens S7 PLCs
MQTT / Sparkplug Bthrough AnvilMQIoT sensors, edge gateways
MTConnectTCP 5000CNC machines
FINSTCP 9600Omron PLCs
MELSEC / SLMPTCP 5007Mitsubishi PLCs
DNP3TCP 20000Power grid, water systems
3D printer APIs80 or 443, Moonraker 71253D printers
PROFINETthrough S7commSiemens PLCs, distributed I/O
EtherCATthrough OPC UAEtherCAT masters such as TwinCAT
HARTthrough ModbusHART field devices behind a gateway
CANopenthrough ModbusCANopen devices behind a gateway
FANUCthrough MTConnectFANUC controllers

How each one is configured is on Connectivity.

Alerting​

Device health transitions raise alerts through the normal pipeline, so a device going Critical reaches you the same way a node going offline does. See Alerts & Notifications.

Roles​

RoleWhat they can do
Global CommandFull management across tenants: register, edit, delete, configure SNMP and credentials
AdminView health and metrics for their tenant, run on-demand checks
EngineerView health and metrics, read-only
OperatorView device cards for their sites

Next steps​