Case
A traffic portal where customers see only their own circuits
Deze case is voorlopig alleen in het Engels beschikbaar.
Samenvatting
Het probleem
Business customers asked for status, traffic and utilisation on their own circuits. The monitoring systems that hold that data show every customer’s ports, so they could never be opened up.
Wat we deden
Built a portal where each customer sees only their own circuits, with live status, traffic history, utilisation, events and scheduled PDF reports, plus an admin console for the NOC. It reads from the monitoring systems already in place, through their APIs and a small plugin, and imports circuits and tenants from the network inventory.
Resultaat
In production for business customers, in two languages, and tested so that one customer can never see another’s ports.
Meer in detail
Built on what the NOC already runs
The existing monitoring systems keep doing the polling they already do, and the portal never polls a router itself: it asks them for the ports that belong to a customer and nothing else. Circuits and the customers they belong to come from the network inventory, so the source of truth stays where the network team keeps it.
Keeping customers apart
A customer portal that leaks another customer’s traffic is worse than no portal. Every request is scoped to the signed-in customer’s circuits on the server, and the tests try to read across that boundary in every way we could think of.
Scheduled reports
Customers can schedule a PDF report of their circuits and receive it by email, without asking the NOC.