Works with the monitoring you already run.
Your monitoring platform already polls your devices. Riopex asks for one read-level key, reads the hourly and daily aggregates, and puts a cost against them.
Request a pilot
The fit
- The reader
- Network operations teams and NOC leads who own the monitoring platform and the circuits behind it.
- The question
- How much traffic did each circuit actually carry, and what did the group pay for that delivery?
- The constraint
- Your devices, your SNMP, your traps and your firewall stay exactly as they are. Reads run on a deliberate request budget, because your own monitoring has first call on that system.
- Where it starts
- One read-level API key to your monitoring platform, and confirmation of which interface belongs to which service. Hourly and daily aggregates are enough for a cost question.
Outcomes
Works with your monitoring
Reading the monitoring system that is already there is a smaller ask than standing up polling infrastructure inside a group's networks, and it starts working in days rather than quarters. The bandwidth capability sets out what the other path would cost.
Coverage on every number
Zero coverage means missing, never zero bits per second. A twenty-minute hour is a one-third-coverage hour. Every sample is used as observed, discarded samples decrement coverage, and a gap suppresses a finding rather than creating one.
Roles before verdicts
Every circuit carries a role, and a role of backup, DR, burst, seasonal, test, out-of-band management or diverse pair blocks a waste finding outright. An unknown role blocks it too, and becomes a data-quality task rather than a red number on your network.
The first month
One key, a binding queue, and a month of reads at a budget your monitoring sets.
- The keyYour team issues a read-level API key to the monitoring system. It is held as a reference into a secrets manager and resolved only when a read runs.
- DiscoveryThe connector lists the interfaces the key can see and proposes bindings to services on the inventory. Exact identifier matches bind, and everything else waits for you in the queue.
- The readsHourly and daily aggregates for the month are read on a request budget with one request in flight per server. The first import is allowed to be slow.
- The rolesEach bound circuit gets a role: primary, backup, DR, burst, seasonal, test, out-of-band management or diverse pair. Roles are what keep a quiet DR link from becoming a red number.
Capabilities that serve this role
Questions from network operations
Will the reads load our monitoring core?
The budget is deliberate: one request in flight per server, aggregates rather than raw samples, and a first import that is allowed to take days. Your own monitoring has first call on the system.
We run two monitoring systems. Which one wins?
Both are read, each binding names its source, and connector policy decides which supplies the denominator where two overlap. The monitoring page states the policy per system.
What happens during a monitoring outage?
The hours without samples are recorded as gaps, coverage drops accordingly, and any figure for that period says so. A gap suppresses a finding rather than creating one.
Can we see what was read?
Every figure names its source and its window, every bound interface shows its binding period, and a rebind opens a new period rather than rewriting history.
A quiet DR link is a working link
- Stance
- It is a circuit doing its job. Backup, DR, contractual minimums, burst headroom and seasonal capacity are all legitimately billed, so the utilisation pane renders neutrally and the word waste is reserved for confirmed billing errors and cleared ghosts. A tool that shows your standby circuit in red has told you it misreads your network, and you will stop trusting the rest of it.
