> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure

> How to enable and configure Prizm's Frequency metrics per column, including regex patterns and thresholds for value and length distribution.

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "Frequency Metrics Configuration",
            "description": "How to enable and configure Prizm's Frequency metrics per column, including regex patterns and thresholds for value and length distribution.",
            "url": "https://docs.dqlabs.ai/architecture/metrics/frequency/configure",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

## Configuring Frequency metrics

Frequency metrics are enabled per column through the Configure Structural Metrics panel. Once active, thresholds and settings are managed on the asset's Metric tab.

1. Navigate to **Metric** in the top navigation.
2. Click **Configure Structural Metrics** (the waveform icon in the toolbar).
3. In the **Map Asset/Attributes to the Metrics** search field, select the target asset and column.
4. Click the **Frequency** tab and check the specific metrics to enable (or **Select All Frequency Metrics**).
5. For **Regular Expressions**, add your regex patterns after enabling the metric.
6. Click **Apply**.

The selected metrics begin collecting data on the next profiling run. To adjust thresholds, navigate to **Asset** → open the asset → **Metric** tab → **FREQUENCY** filter chip → click the metric → **Edit configuration** (pencil icon).

<Frame>
  <img src="https://mintcdn.com/dqlabs/ZKrDEZVwUfowQ-cY/images/image-58.png?fit=max&auto=format&n=ZKrDEZVwUfowQ-cY&q=85&s=43028875981be44b37eca4041516263d" alt="Image" width="1030" height="1238" data-path="images/image-58.png" />
</Frame>

## Configuration options

| Option            | Description                                                       |
| ----------------- | ----------------------------------------------------------------- |
| **Valid**         | Whether a result within the pass criteria counts as a valid run   |
| **Scoring**       | Include this metric in the asset's overall quality score          |
| **Weightage%**    | Relative weight of this metric in the overall score (default 100) |
| **Pass Criteria** | The condition the result must satisfy to pass (default `>= 100`)  |
| **Export**        | Include metric results in data exports                            |

## Threshold

Choose how Prizm determines when to raise a Frequency alert.

**Automated Threshold** — System-generated thresholds based on the historical baseline for each frequency metric. Prizm computes how many standard deviations the current value is from the baseline and maps deviation magnitude to alert priority:

| Priority     | Deviation | Default | Description                                                 |
| ------------ | --------- | ------- | ----------------------------------------------------------- |
| **Low**      | 0σ – 1σ   | Off     | Within expected variation. No action required.              |
| **Medium**   | 1σ – 2σ   | Off     | Moderate deviation detected. Monitor for emerging patterns. |
| **High**     | 2σ – 3σ   | **On**  | Significant anomaly. Investigation recommended.             |
| **Critical** | ≥ 3σ      | **On**  | Extreme deviation from baseline. Immediate action required. |

**Custom Threshold** — User-defined absolute limits for triggering alerts. Useful for setting hard floors on match rates for Regular Expressions (e.g., alert if match rate drops below 95%) or hard ceilings on length ranges.

## Semantic context

Frequency metrics are automatically tagged with:

* **Dimension:** Validity
* **Domain:** Inherited from the asset's domain assignment

To update the semantic context or assign Owners, open the metric in Edit configuration mode and scroll to the **Semantic context** and **Owners** sections.