Netriva Network Monitoring & Operations
Menu
← Guided tour

Guided example

Explore the demo network

Explore the interactive topology, then follow a device through interfaces, monitoring and support.

Demo data — simulated, read-only. These devices, addresses, measurements and incidents are fictional examples. Nothing here is saved to your inventory or sent to a collector.

Visible devices

6

Two routers, three switches and a server

Example connections

5

Port labels and a sample uplink fault

Example sites

Blantyre + Lilongwe

Fictional ITES-style office and branch

Sample ITES-style network topology

Explore a fictional ITES-style network across two sites. Select a router, switch or server for details; zoom or drag to inspect the links. The WAN link illustrates the site connection, not a discovered physical cable.

Simulated example — no live network access or automatic refresh. Use Tab or arrow keys to navigate devices.

Example link states

Green: example link up. Red: example uplink down. Green device icons mean the device still responds in this scenario.

100%

Select a sample device

Explore the six devices shown on the map. Compare the uplink incident with working branch links and a server memory warning.

Selected demo device

Demo Lilongwe Edge Router

Demo: No open incident
Site
Demo Lilongwe Branch
Network / VRF
Branch WAN
Management IP
198.51.100.1
Hostname
edge-router.demo.example
Manufacturer
MikroTik
Model
CCR2004
Software
Example firmware
Profile
Network device — ports & traffic (SNMP)

How the pieces connect

  1. Demo Lilongwe Branch groups the device with its location.
  2. Branch WAN identifies the address network / VRF.
  3. Network device — ports & traffic (SNMP) defines which information to request.
  4. Demo Branch Collector uses approved read-only access to collect it.
  5. Incoming observations populate interface views; rules can open incidents for support.

Example traffic

18 Mbit/s

Simulated demo value

Example CPU

Unavailable in this profile

Simulated demo value

Example memory

Unavailable in this profile

Simulated demo value

Demo interfaces

Example link states and traffic; no actual observations or network checks were performed.

PortConnected toLinkSpeedExample traffic
ether1Blantyre WAN routerUp1 Gbit/s18 Mbit/s
ether2Branch LANUp1 Gbit/s12 Mbit/s

Demo support workflow

No incident in this sample scenario

Review port traffic and link status. Choose a separate BGP profile if you need BGP neighbour information and your router exposes the required MIB.

In real monitoring, unsupported or missing data is shown as unavailable. These sample values do not certify hardware support.

Simulated response example

Respond to network incidents on your phone.

  1. 01

    Detect & notify

    A configured rule opens an incident. Your alert policy selects the site, severity and email recipient or signed webhook.

  2. 02

    Control the timing

    Quiet hours and maintenance windows shape collaboration notifications. A delayed escalation can notify support if the incident remains unacknowledged.

  3. 03

    Respond on mobile

    An authorised engineer can review the incident in the Android companion, assign it to themselves and record incident notes. Offline work stays pending until sync.

Illustrative workflow only. No notifications are sent and no mobile work is synchronised by this demo.

The Netriva advantage

From the first alert to mobile incident response and verified recovery.

Keep monitoring, response and incident evidence in one workflow, with clear visibility when connectivity or data is missing.

Mobile incident response

Use the Android companion to review incidents, acknowledge and assign work to yourself, and capture incident notes. Encrypted offline notes and acknowledgements show their pending sync status. QR scanning, maintenance checklists and private photos support site visits.

Automated alerts you configure

Choose sites, recipients and severity for email or signed webhooks. Set quiet hours, critical overrides, maintenance windows and escalation delays. Keep notification attempts and delivery status alongside the incident.

Continuity through connection gaps

Collectors can buffer observations during WAN interruptions within configured limits. Optional site monitoring can evaluate rules and notify locally when configured. Older evidence keeps its original time when the connection returns.

Evidence you can trust

Missing or stale readings stay visible. Acknowledging an incident records a response; new measurements confirm recovery. Coverage reports show the observed period and data gaps so your team can judge the evidence.

Context for the next action

Connect incidents to devices, interfaces, owners, notes and runbooks. With the required sources configured, verified service dependencies reveal impact and configuration history helps explain what changed.

Your deployment, your access

Choose your own server or ITES hosting. Give people access by workspace, role and site, including the mobile companion. Monitoring uses approved read-only collection and diagnostics.

The Android companion is available to all Netriva users. Sign in with your Netriva account; your workspace role controls the sites and actions you can access. Notification delivery follows your configured alert settings.

Continue the guided tour