Schema and crawler-access alerts show what changed, when, and whether it recovered
recentChanges is the report's change feed: a rolling window of alerts on the two tracked dimensions, so you can see drift (or recovery) without diffing audits yourself.
The feed#
Up to 20 AuditAlert rows for dimensions schema and crawler-access, ordered by lastConfirmedAt descending. Each entry is { dimension, title, description, severity, status, firstDetectedAt, lastConfirmedAt, recoveredAt } — status arrives lower-cased (for example open, resolved), while severity passes through as stored.
Reading a lifecycle#
firstDetectedAt— when the change was first noticed.lastConfirmedAt— when it was last seen still true (this is the ordering key).recoveredAt— when the condition cleared; non-null means it is fixed.
A schema alert that keeps its recoveredAt empty is still broken; one with a timestamp is history. Because the feed is capped at 20 and scoped to two dimensions, treat it as a freshness signal rather than a complete audit trail — the full history lives in the audits themselves (and in the dashboard's change log, see Act in the right layer).