Network Monitoring

The ISP problem isn't lack of equipment — it's finding out something broke after the customer did. Done right, monitoring flips that order.

What network monitoring is

Continuous collection of metrics (CPU, memory, link, BGP session, latency), logs (Syslog, NetFlow) and state (UP/DOWN, threshold) from all infrastructure equipment, with automatic alerting when something goes out of pattern.

Small ISPs get by with SNMP in Nagios and a Telegram bot. Large ones without structured monitoring become hostages to reactive NOC — losing customers because they didn't see the problem first.

What RASYS does with monitoring

  • Zabbix with proprietary templates — not the generic factory ones. Templates for Huawei NE, Juniper MX, Mikrotik, your specific GPON OLT vendor, with items that matter (BGP session, OSPF neighbors, ONU optical power).
  • LibreNMS for inventory — SNMP auto-discovery, automatic topology, traffic map. Good complement to Zabbix.
  • Grafana dashboards — operational view (NOC) and executive view (management). Datasource Zabbix, InfluxDB, Prometheus.
  • NetFlow / sFlow — traffic analysis per application, top talkers, DDoS detection via flow rate spike. nfdump, ELK, ntopng.
  • Structured alerting — Telegram/Slack/email with severity, deduplication, escalation if no one acknowledges. No useless alert flooding.
  • SLA reports — link availability, MTBF/MTTR, exportable for corporate customers.
  • Centralized Syslog — rsyslog/syslog-ng for retention and fast search. Incident forensics in minutes, not hours.

Equipment we work with

Zabbix 6/7, LibreNMS, Grafana, InfluxDB, Prometheus, Elastic/Kibana, ntopng, nfdump, rsyslog, syslog-ng.

When it makes sense to talk to us

You use only basic SNMP and miss critical events; have Zabbix but only with generic templates; customer reported an outage before you saw it; need SLA reports for corporate customers; need baseline data to justify link upgrades.

Talk to us. See also: Firewall, BGP, Main Vendors.