Know a device is down before users do
Every device is checked for availability on the interval you choose. An unreachable host raises a Soron alert, notified in the console, by e-mail, syslog or webhook to your on-call tool.
A switch that stops answering, a firewall at 95 % CPU, an uplink saturated before the morning rush: you want to know before users call. ConnectMyAssets adds network device monitoring to the platform that already knows your devices: availability monitoring over ICMP, health readings over SSH, policies set per asset group and alerts through Soron. No agent, no SNMP community to maintain, no second inventory to keep in sync.
Request a demoEvery device is checked for availability on the interval you choose. An unreachable host raises a Soron alert, notified in the console, by e-mail, syslog or webhook to your on-call tool.
CPU or memory climbing, a temperature rising, a fan or power supply failing: thresholds on health readings turn a slow degradation into an alert while there is still time to act.
Check the data centre core every minute and branch access switches every fifteen. Set it once on the asset group, lock it if needed, and every site below follows.
The Infrastructure monitor watches the machine that runs ConnectMyAssets: disk filling up, database load, background jobs, certificate expiry. You see a problem coming instead of discovering it.
Classic SNMP monitoring is fragile and costs your team hours of setup and upkeep. ConnectMyAssets monitoring is modern and SSH-based: you install it and you get the health of your devices, tied to the inventory you already have.
Monitoring works on the devices already in your CMDB, with the credentials already in your Vault.
Each check sends a short series of ICMP echoes together with a TCP probe on the SSH port, and measures round-trip time and packet loss. A device that filters ping but answers on SSH is not reported down. Interval from 1 minute to 24 hours.
A short SSH session reads CPU, memory, uptime, temperature and the state of fans and power supplies, plus, depending on the vendor and device type, PoE draw, stack members, wireless clients, firewall sessions and HA state, VPN tunnels, BGP and OSPF neighbours.
Interface counters are turned into inbound and outbound rates in bits per second, alongside errors and discards. The dashboard ranks the interfaces with the most traffic right now.
Switch monitoring on or off, set the ICMP and SSH intervals and choose the metrics on an asset group: sub-groups and devices inherit them. Lock a setting at the top and nobody below can change it. Each setting says where it comes from: inherited from France, set here, locked by EMEA.
Host unreachable, high latency, packet loss, high CPU, high memory, any metric above a threshold or in a bad state: the monitoring detectors of Soron raise alerts with the same rules per group, preview, exceptions and notifications as every other alert.
Every numeric metric is kept for charting: recent samples for the last day, hourly averages and peaks over the following weeks. Readings can be filtered, sorted and exported to CSV from the device page.
Monitoring shares the global rate ceiling with discovery scans and never opens a session on a device a scan is using. When every credential is refused, readings stop for that device instead of locking shared AAA accounts. A changed SSH host key ends the session before any credential is sent.
One page with a verdict (healthy, warning, critical), eight key figures with their last 24 hours (CPU, memory, fullest disk, database size, connections, requests per second, response time, queued work), disk forecast, background workers and limits against your sizing profile. Each finding says what to do. One click downloads a support bundle.
Two readers, each with its own interval, both driven by the inventory and the credentials the platform already holds.
The same stateless engine as discovery sends the echoes, each carrying a cryptographic cookie so forged or replayed replies are ignored. Availability, round-trip time and loss are stored per device. IPv6 management addresses are reported as not probed, never as down.
A session separate from inventory collection logs in with the Vault credentials, sends only the commands the enabled metrics need and parses them with the vendor profile. The device serial number is checked so a reading is never stored against the wrong asset.
For each setting, the topmost lock wins, then a device override (metrics only), then the nearest group that sets it, then the platform default. The full chain from the platform default down to the device is shown on screen.
Reading metrics and changing policies are separate permissions, scoped to asset groups. Every policy change, refused change and export of readings is audited and can be forwarded to your SIEM.
Discovery and SSH collection bring your devices into the CMDB with the right vendor profile.
Choose intervals and metrics on the top asset group, refine them on critical sites, lock what must not change.
Enable the Soron monitoring detectors, preview what they would raise, route notifications to your team.
Follow the Monitoring overview, the device charts and the map, and investigate from the device page.
Prepare your project and define your scope.
Because SNMP monitoring is fragile and expensive in human time. Each vendor and each firmware needs its MIBs and OID templates, every device needs a community or an SNMPv3 user, polling has to be tuned, counters can disappear after an upgrade and false alerts pile up, while a separate inventory drifts from the real network. ConnectMyAssets reads device health over SSH, standardised by its vendor profiles, with the credentials already in the Vault. There is nothing to configure on the devices, no agent and no MIB: you install it and you get availability, CPU, memory, temperature and interface data, tied to the same inventory, groups, policies and Soron alerts.
No. Availability is checked with ICMP echoes and a TCP probe on the SSH port, and health readings are taken over SSH with the credentials stored in the Vault. There is no SNMP community or agent to deploy: if the platform can collect a device, it can monitor it.
Every device type gets availability, latency, packet loss, CPU, memory and uptime. Depending on the vendor and type, ConnectMyAssets adds temperature, fan and power supply status, interface rates, errors and discards, PoE draw, stack status, wireless clients and radios, firewall sessions and HA state, VPN tunnels, BGP and OSPF neighbours.
By default every 5 minutes for both availability and health. Availability can be checked from every minute to once a day, SSH health readings from every 5 minutes to once a day. You set the intervals per asset group, so critical sites can be checked more often than branch offices.
Monitoring feeds Soron, the alerting engine of ConnectMyAssets. The host unreachable detector raises an alert as soon as a device stops answering, and you receive it in the console, by e-mail, or forwarded by syslog and webhook to tools such as ServiceNow, Jira, Slack, Microsoft Teams or PagerDuty.
No. Probes and SSH sessions share one global rate ceiling with discovery scans. When a device refuses every credential, its readings are paused instead of retried, so a password rotated on your AAA server cannot lock the accounts of the whole estate. Readings resume when the credential is updated.
It covers network availability and device health directly in the platform that holds your inventory, compliance and vulnerabilities, which is enough for many network teams. If you already run a monitoring platform, ConnectMyAssets works alongside it: alerts can be forwarded by syslog or webhook, and ConnectMyAssets exposes its own metrics to Prometheus-compatible collectors.
It is the health page of ConnectMyAssets itself, reserved for super administrators: host resources, PostgreSQL, background workers, product limits and sizing, with a history up to a year. Each finding states the measured value, the threshold crossed and what to do, and a support bundle can be downloaded in one click.
See what ConnectMyAssets can change for your team. On your infrastructure, with your requirements.
Request a demo