Netmon by Telperion
ISP network visibility, validated one pilot at a time.
Netmon is the product direction behind Telperion’s monitoring work: Core, Edge, Flow, CS, and SWT offerings that connect routing, interfaces, flow, optical telemetry, Ansible workflows, software tracking, error reporting, and AI-assisted operator workflows.
Built around real operational questions
The near-term motion is assessment first, then a controlled pilot if the environment and use case fit. No unsupported hardware promises, no confidential demo data, and no product scaling before validation.
Where is the problem?
Bring topology, interface health, routing context, traffic signals, and error counters closer together so operators can prove whether an issue is access, core, transit, optical, software/version-related, or customer-side.
What telemetry is missing?
Assess current SNMP, NETCONF, flow/JFlow/IPFIX, syslog/Graylog, NetBox, Ansible, backup, software inventory, CVE/release tracking, and dashboard coverage before deciding what Netmon should ingest or visualize for a specific network.
What would a pilot prove?
Define narrow success criteria: outage-domain proof, topology accuracy, customer-impact visibility, error reporting improvements, DDoS/flow insight, software/update visibility, AI-assisted triage, or automation quick wins.
Pilot guardrails
Environment-specific fit
Evaluate the customer’s actual monitoring stack, device mix, telemetry sources, and operational pain before recommending a Netmon pilot.
Safe demo data
Use synthetic, sanitized, or customer-approved data only. Public materials should not depend on confidential topology, configs, screenshots, or device details.
Defined success criteria
Scope pilots around a few measurable outcomes such as outage-domain proof, topology accuracy, flow visibility, error reporting, AI-assisted triage, software/update visibility, or alert-quality improvements.
Product directions
Netmon Core
Monitoring and topology for Juniper-heavy ISP cores: IS-IS/BGP/MPLS context, interface utilization, optical telemetry, alarms, scheduled reports, and NOC-ready operational views.
Netmon Edge
Customer-edge and access monitoring direction: CPE/access health, subnet discovery, site hierarchy, map views, maintenance windows, SLA/availability reporting, and edge-specific alerting.
Netmon Flow
Flow-based visibility for top talkers, traffic profiling, capacity planning, and DDoS investigation where JFlow/IPFIX/NetFlow data is available and operationally useful.
Netmon CS
Support-facing monitoring workflows for customer-impact context, escalation notes, outage summaries, customer/service lookup, and reportable evidence that helps front-line teams communicate clearly.
Netmon SWT
Software version tracking across servers and network devices: Proxmox, Juniper, and Ansible collection; CVE/release checks; subscriptions; notifications; and action reports for what needs updating.
AI-assisted operations
Optional AI integration for customer-controlled workflows: error report summaries, alert/event triage, incident notes, runbook search, report generation, and change-review assistance.
Best-fit early customers
Small and mid-size ISPs
Operators with local or regional decision-makers, BGP/fiber/core complexity, and a need for better monitoring without enterprise procurement drag.
MSPs and data centers
Teams responsible for managed network services, failover validation, customer-facing uptime, colocation, or network-heavy clients.
Discovery-first WISP work
Useful for operator interviews and backhaul/core visibility, but not positioned as a finished RF/tower/CPE monitoring product until those workflows are explicitly built.
Start with a Netmon readiness conversation
We will compare your current monitoring stack, data sources, and operational pain before proposing a pilot.
Discuss Netmon Readiness