Errors and How We Hear About Them

What you see when something goes wrong, and what Frabs is told automatically.

When something goes wrong on one of your servers, you see a plain message where it matters, and the Frabs team is told automatically, with the details your server reported, so we can fix it. You do not need to report it, though you can always open a ticket.

What is reported

What	You see	The Frabs team gets
An install step fails	The reason, in the installer	The step, the error, the OS, kernel and what each platform reported
The sensor reports an error (for example a platform's guest list cannot be read)	Degraded on the server's page, with the reason	Every error, its count and the sensor's health
The server's layout changed	Layout Changed, with what changed	The change
An action fails on the server or in your billing system	Action Failed on the incident	The action, the incident and the error
An alert cannot be delivered	The integration shows Not working	The channel and the error after retries
A server stops reporting	Offline, and an alert	When it was last seen

What is never sent

No traffic and nothing from inside your customers' VMs: only the error and the server's own health details.

PreviousReputation & Abuse Intelligence NextGetting Support