What is Operation Report?
Definition
Different operations produce different report types: a drift report shows differences between a database's actual and expected state, an update report documents which ChangeSets were applied and their outcomes, and a checks report summarizes which Policy Checks passed or failed against a given change. Each report is generated automatically as a byproduct of running the operation itself, rather than requiring a separate step to document what happened. Because reports are generated consistently every time an operation runs, they can be archived over time to build a historical record, useful both for troubleshooting a specific incident and for demonstrating process adherence during an audit or compliance review.
Why Operation Reports matter
An operation that runs without leaving a record is hard to reconstruct later: did the last deployment actually apply every ChangeSet it was supposed to, and did any of them fail silently? Operation Reports answer that question directly, for every operation, without requiring anyone to remember or manually document what happened. That matters for day-to-day troubleshooting and for satisfying an audit that asks for evidence of what ran and when, since the report already exists rather than needing to be assembled after the fact.
How Operation Reports work
Each type of operation, drift detection, an update, a rollback, a Policy Check run, produces its own report format tailored to what that operation actually does. A drift report lists specific schema differences; an update report lists ChangeSets applied and their status; a checks report lists which policies passed or failed. Reports are typically available in both human-readable and machine-readable formats, so they can be reviewed directly or fed into automated tooling for further processing. Older reports can be retained and compared against newer ones to see how a database's change history has evolved.
How Liquibase helps
Liquibase generates Operation Reports automatically for the commands teams already run, drift checks, updates, rollbacks, and policy checks, so documentation of what happened doesn't require a separate manual step. Combined with Structured Logging, Operation Reports give a team both a real-time, queryable stream of activity and a set of discrete, reviewable summaries for specific operations, covering both continuous monitoring and point-in-time audit needs. Many teams archive Operation Reports alongside their deployment records specifically so a compliance review can be answered by pulling existing files rather than re-running historical operations to regenerate evidence after the fact. Comparing reports across a series of deployments over time can also surface slow trends, a gradually growing number of policy warnings, for instance, that wouldn't stand out looking at any single report in isolation.
