How problems are tracked from first sign to resolved, the incident types, and what acknowledging does.
When a check detects a problem, Monitrova opens an incident to track it from first sign to resolution. Incidents are confirmed before they alert you (to avoid one-off blips), grouped by type, and automatically resolved when the site recovers.
| State | What it means |
|---|---|
| Suspected | A first failed check. Monitrova waits for confirmation before alerting, so a single blip doesn't wake you. |
| Open | Confirmed (e.g. a second consecutive failure). This is when the alert is sent. |
| Resolved | The site recovered, the certificate was renewed, or the error cleared — the incident is closed automatically. |
| Type | What it means |
|---|---|
| Down / Recovery | The site failed its uptime check, or came back up. |
| SSL expiring | The certificate will expire within your warning threshold. |
| SSL invalid | The certificate is expired, mismatched, self-signed, or otherwise untrusted. |
| Homepage issue | The homepage returned an error, a blank page, or a backend error was detected. |
| Homepage noindex | The homepage gained a noindex tag that hides it from search engines. |
| Backend error | A PHP fatal, database error or framework crash was detected in the page. |
These tools are one-off checks. A Monitrova account monitors your sites continuously and emails you the moment something breaks.