metabase / metabase/metabase

Method of Deduplicating Metrics

Open
#62,530 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

.Project candidate Administration/Metrics & Segments Organization/Verification & Official Items Semantic Layer/Metrics Type:New Feature
Dominant language
Clojure
Stars
49.3k
Forks
6.8k
Avg merge
1d 13h
Merged PRs (30d)
653

Description

Is your feature request related to a problem? Please describe.
We want to use the metrics system in Metabase but if you allow self service (which is the goal here) it's very easy for metrics to be duplicated (multiple metrics with the same names and multiple metrics with the same definition). We would have to build a process around 'who or what creates metrics' and 'when or where do we adjust / compare those.'

Describe the solution you'd like
On creation of a metric it would be nice if users were notified that a metric with the same definition and/or name already existed. It would also be great to have some centralized way to identify duplicate metric names and definitions that already exist.

Describe alternatives you've considered
Exporting the metrics somehow and tracking them in an external tool, like Airtable, for validation and deduplication.

Additional context
Customer request

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name any files, tests, or entry points. Start by locating the metrics creation and listing flows in the Metabase codebase, then clarify whether duplicate names, duplicate definitions, or both must be detected and how users should be notified. Done should include an agreed design for identifying existing duplicates and handling them during creation.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
analytics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.