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
- Purpose: Set which profiler metrics run by default, per data type, and whether sample data is stored or read.
- Benefits: Gives every new profiler workflow across every team a consistent, already-tuned baseline instead of reconfiguring the same metrics from scratch.
How to Access
Navigate to Settings > Preferences > Profiler Configuration.
Metric Configuration
Metric Configuration lets you disable metrics 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
histogram, cardinalityDistribution, or system, among others. Add them to the Metrics field on the profiler agent if you use the column distribution charts or system data manipulation language (DML) metrics. Upgrading keeps your existing sample settings as Static, but turns Randomized Sample off and removes the deprecated Compute Metrics setting.
Add a row per data type to control which metrics the profiler computes for columns of that type:
- Click Add Field.
- Choose a Data Type, for example
INT,STRING, orTIMESTAMP. Each data type can only be configured once. - Choose which Metric Type(s) to disable for that data type, or leave it on All to disable every metric for that type.
- Use the Disable toggle to turn the whole row off without deleting 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: