Dashboard
Network throughput
Download above, upload below · solid = average, dotted = peak
Sum of subscriber sessions (PPPoE and static clients). Traffic that
goes through no subscriber session — a bandwidth test from a CPE or between routers, device
management — is not in this curve: it shows below, as Not from clients.
Routers — live traffic
Top consumers
Radio backhauls
Saturation risks
Latency by client
Where the delay comes from (by segment: access, next hop, internet)
Load by node
Queues by node
Selection
Health over time
Who consumes
Which services the traffic comes from
Where the traffic goes
Who talks to whom, client by client
Destinations reached
Find an IP
Traffic restrictions
Write a restriction
Service catalogue
Advanced: NetFlow exporters
Your routers are recognised and declared
automatically: the internet exit is counted, each client only once. Declare by hand only
an exporter that is not one of your routers.
Links: throughput, capacity, source
The plan belongs to each client. A site (PoP)
is only a connection point: it has a capacity, not a plan. A client's plan is pushed by
your billing through the API (PUT /model/v1/services, as often as
needed), or set here. The last one written wins. A client with
no plan, including a new one just detected, gets the default plan.
Default plan
Clients
Packages pushed by the API
Commercial reading of the measurements: who is likely to cancel (poor experience, usage collapsing, silent line), who is ready to be sold a bigger plan (lives at its ceiling with a good experience), and how many more subscribers each site can take before quality drops. It compares the chosen period with the one before, so it needs history.