​

Profiler Configuration

Profiler Configuration sets the platform-wide defaults the profiler applies before any individual profiler workflow runs:

• Which metrics it computes for each column data type
• Whether it stores or reads sample data

Setting sensible defaults here means new profiler workflows across every team start from a consistent, already-tuned baseline instead of each owner reconfiguring the same metrics from scratch. These defaults apply to every profiler workflow unless a workflow overrides them. For more information about running the profiler itself, see Profiler Workflow.

​

How to Access

Navigate to Settings > Preferences > Profiler Configuration.

​

Metric Configuration

By default, the profiler computes every available metric for every column. Metric Configuration lets you turn specific metrics off per data type, which is useful when:

• A metric doesn’t make sense for that type, such as computing a mean on a string column
• You want to keep profiling fast on very wide tables by skipping metrics your team doesn’t act on

Add a row per data type to control which metrics the profiler computes for columns of that type:

1. Click Add Field.
2. Choose a Data Type, for example INT, STRING, or TIMESTAMP. Each data type can only be configured once.
3. Choose which Metric Type(s) to disable for that data type, or leave it on All to disable every metric for that type.
4. Use the Disable toggle to turn the whole row off without deleting it.

Click the X button next to a row to remove it.

​

Sample Data Ingestion Configuration

Sample data lets users preview real rows from a table directly in OpenMetadata, which is convenient for spotting data quality issues at a glance, but it also means row-level data is brought outside the source system: Click Save to apply your changes.