What Silent Failure watches

Six kinds of signal from every host, and one rule across all of them: missing data is a finding.

Hosts and containers

State, not just uptime

Online, offline, never seen, and in maintenance. The fourth has no colour, because it is not a verdict.

Expected containers

Tick the containers that should be running. One that stops being there raises an alert; one you never ticked does not.

CPU, load, memory, disk

Hourly aggregates keep a year of history with min, average and peak — because the average alone hides the quarter of an hour a disk was full.

Clock offset

A host whose clock has drifted produces logs and certificates that cannot be lined up with anything else.

Ports, packages and logs

An approved baseline

Approve what is listening now. A new port, or the same port on a new bind address, is then a change you get told about.

CVEs against installed packages

Matched from the OSV advisories against what is actually installed, with the distribution’s own triage and the CVSS score side by side.

Images, not just hosts

Container images are scanned with Trivy, including secrets baked into layers. We store where the secret is, never the secret.

Log errors with context

The matched line plus the lines around it, because a stack trace without its neighbours is just the word “fatal”.

SSH and sudo

Accepted, failed, and invalid users over the last day, per host.

Checks from outside

HTTP, TCP, ping and DNS from outside your infrastructure, with certificate expiry and the TLS version actually negotiated.

See it on your own machine

One host is free, and the install takes a single command.

Start freeRead the install docs