The Database Changes, Policy Checks, and Drift Detection views share one filter bar. One filter state per page drives both the headline metrics and the operations list, so the two always reflect the same set of runs.

Common filters

Every view offers the same core filters. Time range covers 7, 30, or 90 days, all time, or a custom range with start and end dates. A custom range starts no earlier than August 1, 2026 and ends no later than today. The other common filters are project, database connection, changelog, outcome, and a free-text search. Search matches the operation id, deployment id, command, and the connection, changelog, and project names. A first visit starts at the 30-day default with everything else unset.

Active filters render as removable chips with a Clear all control. When no operations match, the empty state echoes the active filters and offers to clear them, or to widen the time range.

Filters specific to each view

• Database Changes: Command type, which matches by command group rather than by an exact command. Update, Rollback, and Changelog Sync each match every command in their family, so Rollback also finds rollback-count and rollback-to-date.

• Policy Checks: Severity, category, and check. Choosing a category narrows the check picker to that category's checks.

• Drift Detection: Drift presence and change type. Filter to detections, clean runs, or all, and to added, removed, or modified objects.

A filter renders even when your data contains only one option, so the bar keeps the same shape for everyone.

Period comparison

Each metric card shows the current period plus up to three prior windows of the same length, so a 30-day view compares against the three prior 30-day windows. Hover over a prior period to see its value and the dates it covers. A period with insufficient data is de-emphasized rather than shown as a misleading zero.

Note: Custom and all-time ranges show the current value only. A custom range has no unambiguous prior period, and all time has no prior period at all.

Saved views and shareable URLs

Saved views are private to you and are the way back to a recurring view. Save the current filters from the filter bar. The saved state captures every active filter, including the view-specific ones and the search term. Views can be renamed, updated to the current filters, and deleted. Names are unique per user and capped at 100 characters. The dropdown groups entries into views that apply to the current page and views for the other operation types, which navigate there with the filters applied.

Active filters are also encoded in the page URL. Reloading preserves them, and sharing the link reproduces the view. Copy link in the filter bar copies the current filtered URL, so you do not have to take it from the address bar. Access is enforced server-side regardless of the URL, so a shared link never widens what a recipient can see.

URLs are shareable and saved views are not. A new session always starts at the page defaults, not your last view.

Why attribution matters here

Operations are filterable by the records they were linked to when they ran, which is why registration and identifiers matter. See Set up monitoring end to end.