Skip to main content

Run History & Metrics

Viewing Maintenance History​

The History sub-tab lists every maintenance run for a table, including before/after metrics for completed runs. It's the quickest way to see what ran, why it ran, and what changed.

Maintenance History tab showing a list of maintenance runs with time range, operation type, and status filters | IOMETEMaintenance History tab showing a list of maintenance runs with time range, operation type, and status filters | IOMETE
  1. Go to Governance > Data Catalog from the side panel.
  2. Find and open the table details page:
    • Data Catalog tab: Search for the table by name and click it.
    • Data Explorer tab: Navigate through Catalog > Database > Table.
  3. Go to the Maintenance tab.
  4. Click the History sub-tab.
  5. Use the filters at the top to narrow results:
    • Time range: a date-range picker (maximum range is 30 days).
    • Triggered by: filter by the username who triggered the run.
    • Operation type: filter by a specific operation.
    • Status: filter by status (All, Pending, Running, Completed, etc.).
  6. To see metrics for a completed run, click to expand a Completed row that has metric data. The expanded row shows a metrics table with Before and After values.
Expanded completed maintenance run row showing before and after metrics table | IOMETEExpanded completed maintenance run row showing before and after metrics table | IOMETE
  1. To see the error message for a failed run, hover over the Failed status badge.
Maintenance History failed run with error message tooltip visible on hover over the Failed status badge | IOMETEMaintenance History failed run with error message tooltip visible on hover over the Failed status badge | IOMETE
  1. The Reason column shows why an operation was scheduled: which threshold condition was met (small average file size, high delete-file ratio, excessive snapshot count, etc.) or whether it was a manual trigger.
Maintenance History row with the Reason column showing the threshold condition that triggered the run | IOMETEMaintenance History row with the Reason column showing the threshold condition that triggered the run | IOMETE

Metrics Per Operation​

OperationMetrics (before/after)
Rewrite Data FilesData File Count, Total File Size
Expire SnapshotsSnapshot Count
Rewrite Manifest FilesManifest File Count, Manifest Total Size
Cleanup Orphan FilesTotal Data File Count, Total Metadata File Count, Total Data File Size, Total Metadata File Size

Manually Triggering an Operation​

Run any maintenance operation on demand without waiting for the automated cycle. This is useful when testing your configuration or addressing an urgent performance issue.

  1. Go to Governance > Data Catalog from the side panel.
  2. Find and open the table details page:
    • Data Catalog tab: Search for the table by name and click it.
    • Data Explorer tab: Navigate through Catalog > Database > Table.
  3. Go to the Maintenance > History sub-tab.
  4. Click the Trigger button in the table header.
Maintenance History tab with the Trigger button highlighted in the table header | IOMETEMaintenance History tab with the Trigger button highlighted in the table header | IOMETE
  1. In the modal, select the operation type from the dropdown.
Trigger maintenance operation dialog with a Select operation dropdown and Cancel and Trigger buttons | IOMETETrigger maintenance operation dialog with a Select operation dropdown and Cancel and Trigger buttons | IOMETE
  1. Click Trigger to confirm.

The operation is queued immediately and shows up in the history list with a PENDING status. The history list refreshes automatically after the trigger succeeds.

Before Triggering
  • Both table maintenance and the specific operation must be enabled.
  • If a job for the same table and operation is already pending or running, the trigger is rejected. Only one active job per table/operation is allowed at a time.

ON THIS PAGE