Where to check status, and what incidents look like
Two different kinds of health information exist, and keeping them separate prevents confusion.
Your projects' posture — what the probes found, when they last ran, whether any scan failed — lives in the application and is specific to you. The health of RowShield itself — whether the probe fleet, the web application and notification delivery are operating — lives on the status surface linked from the application footer, and is the same for everyone.
What incidents look like
An incident notice states plainly what is affected, since when, and what we are doing about it. Notices name components — probe fleet, web application, notifications, storage scanning — and say whether scans are delayed, degraded or halted.
Updates are timestamped as the situation develops, including at the moments when we know less than we would like: an honest partial picture beats a confident guess. Resolution entries state what failed, what the impact was and what changed to prevent a repeat, in plain sentences rather than euphemism.
Scheduled scans that could not run because of an incident are marked as missed rather than silently skipped, so your history stays truthful; backfills happen where the underlying data allows them, and the notice says when they do not.
Our communication standard
Three commitments govern how we communicate during problems. We report what we know when we know it, including the moments when the honest answer is that investigation continues. We distinguish clearly between measurements we took and conclusions we drew, so you can weigh the evidence yourself.
We do not mark an incident resolved until the underlying condition is corrected, not merely hidden; a workaround that masks symptoms is described as exactly that. After significant incidents, a written summary follows once the cause is properly understood, because a fast wrong explanation helps nobody.
The same standard applies in miniature to degraded-but-working states: when probes run slower than usual or delivery lags, the status surface says so with numbers rather than reassurance, because quiet degradation is how trust erodes.
Related
Did this answer your question? If not, tell us what is missing — article corrections go straight to the person who maintains it.