Collect signals
Device telemetry, SNMP, supported native transports, and cloud inventory enter a tenant-scoped pipeline. Which other monitoring tools we take alerts from first is decided with our early-access customers.
Network operations platform
From alert storm to an incident an engineer can act on.
AssureMesh sits on top of the monitoring tools your team already runs. It collects network evidence, finds the root cause, shows which devices, sites and business applications a fault touches, and suggests remediation steps and commands for the engineer to review. It is read-only by default.
The operational workflow
Each stage has a distinct job and a distinct failure state. The product should never convert missing evidence into false certainty.
Evaluate conditions
Deterministic detectors evaluate reachability, interfaces, resources, routing state, temperature, and configured tenant thresholds.
Reduce duplicate symptoms
Related alarms are grouped on a Correlations view. Unrelated failures stay visible instead of being hidden by over-broad grouping. How parent and child grouping works in your environment is shaped with our early-access customers.
Assemble RCA
The incident includes ordered evidence, a blast radius of affected devices, sites and business applications, and an explicit likely cause. Diagnosis starts from deterministic pattern matching and works without an external AI provider.
Suggested remediation
Suggested steps and commands, with the diagnosed cause and the risk reasoning behind them. The engineer runs every command.
Past incidents, trends and reports
Historical telemetry supports deterioration and capacity signals while the incident timeline records acknowledgment, ownership, and recovery. Similar past incidents surface with where and when they happened (this device, another device at the same site, or another site), the root cause recorded for them and what was recommended then, for incidents recorded from now on. An RCA report can be generated on demand from an incident's timeline and evidence.
Deployment choices
Customers do not have to expose management interfaces to the public internet.
Cloud control plane
Tenant portal and analysis services run in AssureMesh-managed cloud infrastructure while an authenticated collector reaches customer devices.
On-premises collection
An edge agent runs at the customer site and streams scoped telemetry outward. Device credentials remain in the configured secret store.
Hybrid or on-premises evaluation
Deployment can be scoped around your security requirements. Exact topology and support boundaries are documented before onboarding.
What read-only by default means
- Monitoring-only device credentials are preferred.
- Monitoring, incidents, RCA, blast radius, assignment, thresholds, and guided steps remain available.
- Write actions are blocked in the platform, not just hidden on screen.
- Every decision goes in a tamper-evident audit log. Each customer is a separate tenant with isolated data.
What it does not mean
- It does not guarantee every vendor alarm is supported.
- It does not make uncertain RCA certain.
- It does not replace the customer’s change process.
- It does not claim field outcomes from test measurements.