Understand drift history

Drift is a timeline as much as an event. A database that drifts once is an incident. One that drifts monthly is a process problem. The history for each database shows past detections and their outcomes, so you can tell resolved drift from recurring drift.

Drift age

Each detected change carries a drift age, for example first detected 5d ago. The age is calculated from the earliest prior drift check on the same database connection where the same object showed the same change, and it keeps counting up the longer a change goes unaddressed. A large age on a recurring item tells you a drift is long-standing rather than new.