Measure asks how database change delivery and governance are performing across the organization. It works on aggregates: rates, coverage, and patterns across many operations over a window of time.

That is what separates it from Monitor. Monitor works on individual operations and current state, so you go there to find a deployment, a policy result, or a drifted database and see what it says. Measure works on many of them at once. Liquibase Secure server computes these across the Database Changes, Policy Checks, and Drift Detection dashboards, and this section is where they are defined and put to use.

Start here

• View governance and delivery dashboards — The Operations Dashboard, the windows behind each section, and how to read a metric tile.

What the figures mean

• Measure deployment performance — The four delivery figures, and the rules Cycle Time uses to decide which changesets count.

• Measure governance effectiveness — The six policy figures, what actually counts as a pass, and what coverage divides by.

• Measure drift across your databases — The five drift figures, which of them deduplicate, and which direction each should move.

Putting them to use

• Analyze patterns in policy failures over time — Get from a moving pass rate to the rule behind it.

• Compare applications, teams, and environments — Projects are the dimension you compare on.

• Identify areas requiring attention — Narrow the estate to what needs someone to look at it.

• Track improvement over time — Decide what should move, then check whether it did.

• Track KPIs and OKRs — Map the indicators you already report on onto the figures the server computes.

Then act on what you found

Measurement tells you where to look, not what to do about it. To take a specific failure, drifted database, or policy violation through to a fix, see Investigate and mitigate issues.