Skip to content

[branch-48] Custom Metrics#30

Merged
gabotechs merged 1 commit into
branch-48from
branch-48-custom-metrics
Jun 12, 2025
Merged

[branch-48] Custom Metrics#30
gabotechs merged 1 commit into
branch-48from
branch-48-custom-metrics

Conversation

@gabotechs
Copy link
Copy Markdown

Cherry pick apache#16195

…6195)

See this issue: apache#16044

The MetricValue enum currently exposes only single-value statistics:
counts, gauges, timers, timestamps, and a few hard-coded variants
such as SpillCount or OutputRows.

However there's often the need for custom metrics when using custom
PhysicalPlans. At Datadog for instance we had the need for tracking the
distribution of latencies of the sub-queries issued by a given phyiscal
plan to be able to pin-point outliers.

Similarly tracking the topN slowest sub-query is something that has been
quite useful to help us debug slow queries.

This PR allows each user to define their own MetricValue types as long
as they are aggregatable. A very basic example is included in the PR
using a custom counter.

(cherry picked from commit fbafea4)
@gabotechs gabotechs merged commit d2745b8 into branch-48 Jun 12, 2025
54 of 55 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants