Service quality monitoring
QoS monitoring for business and corporate subscribers
Every individual circuit is monitored on its own in Zabbix — traffic, link load, the real use of the committed rate and connection stability, in real time.
The problem
"The link is slow" — and nobody can prove otherwise
A dispute with a business customer almost always starts the same way: the customer says the bandwidth is not there, the operator says everything is fine. Without per-circuit history both sides are arguing from impressions. A graph ends that conversation in a minute — and often shows the link genuinely is not enough any more and needs an upgrade.
- The complaint arrives; the evidence does not
- Peaks are noticed only when it is already too late
- Nobody spots the need for an upgrade in time
- An outage is not recorded, so it cannot be analysed
What we deliver
QoS monitoring for business and corporate subscribers
Inbound and outbound traffic
IN and OUT separately, per circuit — not just a total on the port.
Link load and peaks
Maximum figures and how often they repeat — the peak shows up first, the average only later.
Committed rate usage
How much of what the customer pays for is actually used — an upgrade or tariff conversation starts from this number.
Stability and availability
Link stability, outages and their duration — recorded, not recalled.
Historical graphs
Day, week, month — load analysis and the trend that capacity planning rests on.
Alerting in time
Detecting the problem and raising the right notification — before the customer calls.
Architecture
Architecture
- 01CircuitEach link is measured on its own
- SNMP
- ICMP
- Zabbix
- 02MeasureInbound, outbound and the peaks
- 03ThresholdActual use of the committed rate
- Triggers
- Percentiles
- 04AlertBefore the complaint, not after it
- Telegram
- 05HistoryGraphs for planning the upgrade
- Zabbix graphs
- Grafana
- 06ReportThe evidence, when a dispute arrives
Operator consoles
Operator consoles
These exact systems run on the group's own infrastructure — the screenshots are processed before publication.
One circuit, one graph — QoS in real time
This is what one business circuit looks like in Zabbix: inbound and outbound traffic, peaks, the real use of the committed rate, and history. It is the graph that answers "is the link actually enough" — and the customer can see that answer too, not only us.
Capabilities
Capabilities
Every item is marked: verified production experience, or engineering capability.
Per-circuit monitoring
ProvenEvery business circuit is its own object in Zabbix, with its own history, thresholds and graphs.
- Zabbix
- SNMP
- per-interface
Thresholds and alerting
ProvenSaturation, outage and anomaly thresholds by severity, with escalation routing.
- triggers
- Telegram
- escalation
History and capacity analysis
ProvenLong retention and trends — the need for an upgrade is argued with a number, not a feeling.
Customer-facing reporting
CapabilityA periodic report, or access to their own graph — the transparency that gets ahead of the dispute.
SLA measurement
CapabilityAvailability measured against agreed targets, where the contract defines them.
Technology stack
Technology stack
- Collection
- ZabbixSNMPICMP
- Visualisation
- Zabbix graphsGrafana
- Alerting
- TriggersTelegramEmail
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.
Fully managed
We own the agreed operational scope end to end.
Use cases
Use cases
A dispute about bandwidth
The customer insists the link is not enough. The graph shows whether that is true, or whether the problem is inside their own network.
Planning an upgrade
Peaks have been climbing for months — the commercial conversation starts from a fact, not a guess.
Post-incident analysis
When it started, how long it lasted, and whether it coincided with anything else in the network.
FAQ
FAQ
Can the customer see their own graph?
Yes — either through a periodic report or with restricted access to their own circuit only. Transparency resolves most disputes before they start.
How often is it measured?
A one-minute interval by default, more often on critical circuits. History is aggregated, so the trend survives months later.