metabase / metabase/metabase

Visual telemetry for questions

Open
#33,501 1 comment 1 reaction 0 assignees View on GitHub
.Performance Querying/GUI Querying/Native Querying/Notebook 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 don't want anyone shooting on their feet when they build stuff on Metabase right? well, when cars were invented people used to go very fast and crash, or over pedestrians, till traffic lights were invented. We need to do the same for Metabase, so people know about the impact of their decisions.

**Describe the solution you'd like**
I would like to visually show users:
- time it takes to compile the query (if it's a GUI query)
- time it takes to run the query
- time it takes to render the query on screen

**Describe alternatives you've considered**
I have to get this info from many places

**How important is this feature to you?**
Important for me as a success eng since many debuggings would be simpler

**Additional context**
A sibling of https://github.com/metabase/metabase/issues/10007. We could also have the score of the question in order to have a visual representation of how difficult the question is to the DW

Contributor guide

Open the contributing guide

Research direction

The issue does not name files, tests, or entry points. First map where GUI query compilation, query execution, and on-screen rendering are handled, then clarify the intended visual telemetry and how completion should be verified across those stages.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
analytics, data-visualization
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.