NETWATCH
NETWATCH has moved.
Why it was separated
NETWATCH does one narrow thing — it watches network links, learns their rhythm, and predicts congestion before it bites — and it does that thing beside whatever system it is monitoring rather than inside it. That independence is what made it useful, and it is also what makes it a better standalone project than a feature of something larger.
It has no dependency on the rest of VALIS, carries none of the data standards or labelling machinery, and is useful to anyone running services over a constrained link. There was no good reason for it to stay bundled.
What you get, and what you don’t
What it does
- Learns each link’s 24-hour baseline and forecasts saturation ahead of time.
- Runs as a standalone process, so it keeps reporting when the monitored node dies.
- Sites share small signed summaries under a hard bandwidth cap.
What it isn’t
- Audited. The test suite is the author’s own; there has been no independent security review.
- Supported. It is published as-is, and maintenance expectations are set in the repository README rather than implied here.
- A product. Nothing about it is for sale, licence or deployment.
The code, the tests and the honest limitations are all in the repository. This page exists so the old URL leads somewhere rather than nowhere.