Skip to content

Edit a Metric Check

Step-by-step tutorial for changing an existing Metric check: its limits, its filter clause, or, before its first Scan, its field and comparison. For which values can and cannot change, see the API page's editable and immutable lists.

Permission Required

You need the Author team permission on the datastore to edit an Active check, or Drafter to edit a Draft. See the Permissions page for the full matrix.

Only changing Min and Max?

The Observability chart has an inline editor for the limits alone. See Edit Threshold.

What Happens to Existing Anomalies

Saving the edit changes only the check. The anomalies it already produced are not deleted, modified, or re-evaluated at save time.

The updated rule takes effect on the next Scan of the container: run one manually or wait for the scheduled operation. Until that scan runs, the anomaly list stays exactly as it was. On that scan:

  • A new anomaly can appear. If the check still fails, a new Record Anomaly is reported. When Archive Duplicate Anomalies is on, a finding that matches an anomaly that is still open (same check, same fingerprint) is archived as Duplicate instead of opening a new one.
  • Old anomalies stay open. Anomalies raised under the previous configuration keep their status until you triage them, or until a Full scan with Auto Resolve resolves what the updated rule no longer flags.

Editing the limits does not reset the check's history: a change comparison keeps comparing with its last measurement.

Steps

Step 1: Select the source datastore from the left menu, then click the Checks tab.

Step 2: Locate the check you want to edit and click it, or open its Settings menu and select Edit . The Authored Check Details form opens.

Step 3: Change the values you need in each section of the form. Each field is described in the create how-to's Field reference.

  • Target: the Filter Clause and the Custom Anomaly Description. The Field too, but only if no Scan has included the check yet. After that, the form shows it disabled.
  • Properties: the Min and Max limits. The Comparison too, but only if no Scan has included the check yet.
  • Ownership: the Owner and the Anomaly Assignee.
  • Metadata: the Description, Tags, and Additional Metadata.

Locked after creation

The table or file the check runs against and the Rule Type are locked once the check is saved. The Field and the Comparison are locked after the first Scan that includes the check. To change any of them, create a new check and archive the old one.

Step 4: Click Validate to test the updated configuration without saving it. A success message confirms the rule can run. If validation fails, see Troubleshooting. The Validate button needs the Author team permission, so it does not appear for a Drafter, who can skip this step.

Step 5: Click Update. A success message confirms that the check was updated.