Can Glossary Metrics be used as native Data Insights KPIs in OpenMetadata 2.0.3?

[meriiiiiiiiiiii]

Hi OpenMetadata team,
I’m working on an OpenMetadata 2.0.3 implementation for a Data Governance project at a bank.
We are building a Business Glossary and would like to measure its maturity directly within OpenMetadata. We have metrics such as:

• Total Glossary Terms
• Description Coverage %
• Owner Coverage %
• Reviewer Coverage %
• Physical Mapping Coverage %
  We can calculate these using Profiler Custom Metrics against the OpenMetadata metadata database. However, these custom metrics do not appear in the Data Insights → KPI → New KPI metric/chart selection.
  We also created a Metric entity (Glossary Term Count) and linked it to a Glossary Term, but it still cannot be selected as a Data Insights KPI.
  Is there a native way in OpenMetadata 2.0.3 to display Glossary-level/custom metrics as KPIs in Data Insights, without developing a custom application or using an external dashboard?
  If this is not currently supported, is there a recommended native approach or is it planned for a future release?
  Thank you!

[IlyaKhalafi]

In 2.0.3, those are three separate features. Profiler Custom Metrics and catalog Metric entities do not register a metric for the Data Insights KPI picker.

The supported KPI creation API has the same restriction, so changing the dropdown alone would not be enough. The 2.0.3 KPI request schema accepts only these four dataInsightChart values.

percentage_of_data_asset_with_description_kpi
percentage_of_data_asset_with_owner_kpi
number_of_data_asset_with_description_kpi
number_of_data_asset_with_owner_kpi

The UI mapping exposes description and owner, each as a number or percentage. On the server, KpiMapper resolves that value as a Data Insights custom chart. It does not resolve a catalog Metric or a Profiler Custom Metric. KpiRepository then evaluates that chart through the search backend.

That explains why creating a Metric entity, linking it to a Glossary Term, or computing SQL profiler metrics does not make it selectable. Those objects do not feed this KPI creation contract.

There is a separate Data Insights custom-chart layer. Its asset-type schema includes glossaryTerm, and the field mapping configuration includes glossary fields such as reviewers and usage count. Having glossaryTerm as a custom-chart asset type does not add charts to the New KPI form or make Profiler and catalog Metrics selectable there.

I have not validated a native custom-dashboard recipe for all five measures, or an alternative API mutation route, so I would not claim that every native reporting route is impossible. What the 2.0.3 source establishes is the restriction in the KPI picker and create request. A supported arbitrary glossary KPI would need that creation contract and UI to accept the relevant Data Insights chart, rather than another SQL profiler metric.

For a feature request, I would specify the numerator and denominator for each measure, especially whether physical mapping means a term tagged to at least one asset or some other relationship. That makes it possible to assess a Glossary-specific chart and KPI path. I cannot confirm a release plan. These checks are against the 2.0.3 schema, UI and server source, not a running deployment.