Tag: monitoring
-
Status: the lab stops being one machine
The second physical server is online. For the first time this project is not one computer with a lot of ambition attached to it.
-
Exit 3 means either
A new test suite reported a problem on two healthy gateways. The lab’s monitoring notes said drift was zero on both machines. One of the two had to be wrong, and finding out which produced a defect worth more than…
-
Why CrowdSec
Anything with a public address is attacked continuously, within minutes of existing, by software that is not interested in what it found. The rented gateways in this lab carry that traffic all day.
-
The check that punished uptime
A test asserted that the tunnel between two servers was up. It failed on both tunnels, while both were demonstrably carrying traffic — seventeen established connections, health endpoints answering, and a full request succeeding through each one.
-
Status: the loop is closed
The tunnel from the rented edge to the house is up and carrying traffic. That was the last structural piece of the original design never exercised end to end, and it has now been exercised in both directions.
-
If the watcher dies, its last words are reassuring
The monitoring system was switched off for eighteen minutes. Every monitor reported UP for the entire period.. Status 1 is UP. Both rows were real, correct, and eighteen minutes old.
-
Status: the first VMs, and the tier they unblock
Three virtual machines exist. After weeks of rented gateways and documents, something is finally running on hardware in the building.