Yuno Network — NOC Documentation
How to run network monitoring for the Yuno Network operations center. Start here, then jump to the guide for your role.
What this is
This is the operations handbook for the NOC monitoring platform. It covers the daily monitoring routine across all projects, how outages are diagnosed and escalated, a reference for every screen, and the full list of URLs — including the public observer pages that need no login.
The single rule that runs through everything: a site visit is the last resort. Always take the cheapest remote action first and escalate only when it's exhausted.
The daily loop
Coordinators check which sites are down (and which have been down the longest), diagnose and call the beneficiary, and — if it can't be fixed remotely — hand off up the ladder. IT Support attempts remote fixes; only genuine physical faults reach a field technician.
Check the provider cloud / remote reset
Coordinator → IT Support
Look at the provider cloud/controller for the device's status and logs. If it is reachable or flapping, attempt a remote reset/reboot. Most outages clear here.
Call the site contact
Coordinator
If the remote reset does not bring it back, call the beneficiary/site contact to ask what is happening on the ground (power brownout, weather, unplugged router) and have them power-cycle the router.
Recommend a site visit
Dispatch Installer
ONLY if the remote reset failed AND an on-site restart also did not work, or the contact reports physical/hardware damage. Only then send a technician.
Who does what
- Coordinators — first line. Find what's down, diagnose, call the beneficiary, escalate.
- IT Support — remote diagnosis and provider-cloud resets; decide whether a dispatch is truly needed.
- Installers / Field Technicians — dispatched only for physical faults, as the last resort.