Monitoring & observability
Flow analytics
NetFlow, IPFIX and sFlow — traffic visibility, peering analysis and cost optimisation.
Architecture
Architecture
- 01CollectPolling + streaming + flow
- SNMP
- gNMI
- NetFlow/IPFIX
- 02Process
- Telegraf
- Akvorado
- Vector
- 03StoreTime series and flow
- Prometheus
- InfluxDB
- ClickHouse
- 04Visualise
- Grafana
- Zabbix
- 05AlertRouting and escalation
- Alertmanager
- Telegram
- PagerDuty
Operator consoles
Operator consoles
These exact systems run on the group's own infrastructure — the screenshots are processed before publication.
Where the traffic actually comes from — flow analytics
Flow records grouped into ASN categories: CDN/OTT, Georgian ISPs, the group's own networks and international transit. This is the picture that decides which cache to bring inside the network, where peering pays for itself and what stays on paid transit. It is the one screen published legible — everything in it is an aggregate share, with no customer and no address anywhere.
Who is actually sending the traffic — per ASN
The same flow data, this time with names on it: which CDN and which platform sends the most, where it lands and which router carries it. This list is what turns a peering or cache-placement conversation into an argument with evidence — Akamai, Fastly, Meta, Google. The volumes are blurred; the names and the proportions are not.
Capabilities
Capabilities
Every item is marked: verified production experience, or engineering capability.
Site power and batteries
ProvenBattery 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
ProvenPolling stays the baseline mechanism across most of the fleet — counters, availability and interface state.
- SNMP
- Zabbix
- LibreNMS
gNMI streaming telemetry
CapabilityStreaming telemetry replaces polling only where the sampling rate demands it — elsewhere the two complement each other.
- gNMI
- gnmic
- Telegraf
Flow analytics
CapabilityNetFlow/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
ProvenThe 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
CapabilityCapacity forecasting
CapabilityGrowth 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.