Skip to content

Monitoring & observability

Network observability

SNMP polling, synthetic checks and routing state on a single dashboard.

Architecture

Architecture

  1. 01CollectPolling + streaming + flow
    • SNMP
    • gNMI
    • NetFlow/IPFIX
  2. 02Process
    • Telegraf
    • Akvorado
    • Vector
  3. 03StoreTime series and flow
    • Prometheus
    • InfluxDB
    • ClickHouse
  4. 04Visualise
    • Grafana
    • Zabbix
  5. 05AlertRouting and escalation
    • Alertmanager
    • Telegram
    • PagerDuty
SNMP, telemetry and flow together — each at the layer where it works

Operator consoles

Operator consoles

These exact systems run on the group's own infrastructure — the screenshots are processed before publication.

Blurred Grafana dashboard showing traffic gauges for upstreams and peering sessions.

Bandwidth and peering in real time

Every upstream and every peering session is measured separately, with global and local traffic split apart. Capacity and peering decisions come from this view — not from a hunch.

GrafanaZabbixper-peerIXP
Blurred AS Upstream analyser showing a per-prefix visibility table across three transits.

BGP visibility per upstream

Each prefix and how visible it is through each transit — which upstream propagates which prefix, and in what share. This is how a route leak, a missing announcement or a mis-built policy becomes visible before it becomes an incident. The tool is public on noc.com.ge.

BGPper-prefixRPKIpublic tool
An automated BGP report from four locations — loss and latency per prefix, with a priority verdict at the end.

Global BGP Report — automatic, every day

From four international vantage points — Sofia, the USA, Amsterdam, India — every one of our prefixes is measured for reachability, loss and latency. No human assembles this: the system compares a 3-hour window against a 24-hour baseline, picks out the direction that is degrading and assigns the priority itself — in this frame P1 is India, where RTT passes 190 ms.

BGPpacket lossRTTautomated
A network map of wireless links — each node showing client count, CCQ, noise floor, airMAX quality and capacity, distance and frequency; hostnames removed.

One map — MikroTik, Ubiquiti and Cambium together

A small or mid-sized operator's network is rarely single-vendor: MikroTik in the core, Ubiquiti on the wireless links, Cambium at the access layer. This map carries, per link, what operations actually runs on — wireless clients on the sector, CCQ, noise floor, airMAX quality and capacity, distance, frequency, Rx/Tx and uptime. The tower power nodes sit on the same map: battery voltage is a metric like any other here, and it explains half of the night-time outages.

MikroTikUbiquitiCambiumairMAXSNMP
Blurred LibreNMS dashboard with a device availability map and alert history.

Network inventory and health

Over 130 devices and thousands of ports in one system: an availability map, alert history and the top errored interfaces — including the GPON/EPON access layer, where a fault shows up on the port before the subscriber notices it.

LibreNMSSNMPGPON/EPONalerting
Blurred OpenPath NOC console showing service status, latency sparklines and an incident feed.

OpenPath — our own NOC console

Live path monitoring on a 15-second refresh: latency and packet loss to each service, including cache servers hosted inside individual operators. A path change is recorded as its own incident, with filters by ASN, ISP and customer. We wrote this tool ourselves because no off-the-shelf product answered the question.

in-houselatency / losspath changeper-ASN

Capabilities

Capabilities

Every item is marked: verified production experience, or engineering capability.

Site power and batteries

Proven

Battery voltage, the mains feed and temperature on the same map as the traffic. A sagging voltage is visible before the outage — and it explains the share of night-time incidents that otherwise stays unexplained.

  • SNMP
  • Battery voltage
  • Temperature

SNMP polling at scale

Proven

Polling stays the baseline mechanism across most of the fleet — counters, availability and interface state.

  • SNMP
  • Zabbix
  • LibreNMS

gNMI streaming telemetry

Capability

Streaming telemetry replaces polling only where the sampling rate demands it — elsewhere the two complement each other.

  • gNMI
  • gnmic
  • Telegraf

Flow analytics

Capability

NetFlow/IPFIX/sFlow on ClickHouse for peering and traffic analysis.

  • Akvorado
  • ClickHouse
  • IPFIX

Grafana dashboards

Proven
  • Grafana
  • Prometheus
  • InfluxDB

Zabbix infrastructure monitoring

Proven
  • Zabbix
  • SNMP traps
  • Agents

Device inventory and port monitoring

Proven

The whole device fleet and its ports in one system — with autodiscovery, an availability map and ranked error counters, down to the GPON/EPON access layer.

  • LibreNMS
  • SNMP
  • GPON/EPON

SLO and error budgets

Capability

Capacity forecasting

Capability

Growth trends and saturation forecasting for links and storage.

Technology stack

Technology stack

Metrics
PrometheusInfluxDBZabbixLibreNMSVictoriaMetrics
Telemetry
gNMIIOS XR telemetryTelegraf
Flow
AkvoradoClickHouseNetFlow v9IPFIXsFlow
Visualisation
GrafanaZabbix UI
Alerting
AlertmanagerGrafana AlertsTelegram

Engagement model

Engagement model

Project

A one-off scope: audit, migration or implementation with a fixed outcome.

Retainer

Monthly engineering hours — specialist access on demand.

Co-managed

NetWizard and your in-house team together, with split responsibility.

FAQ

FAQ

Zabbix or Prometheus?

Both, for different jobs. Zabbix is strong for appliance and agent monitoring; Prometheus for dynamic, containerised environments. They frequently coexist under one Grafana.

How long is data retained?

Retention is designed against budget and requirement — high resolution short-term, aggregated data long-term.

Tell us about your infrastructure